Hi

On Wed, Jun 11, 2014 at 8:52 AM, Matthew Miller  wrote:

This is kind of sentimental, and I think possibly Seth would not have liked
to have a big deal made of it, but... I guess I'm going to anyway. I would
like to keep the "yum" name in remembrance of his contributions. This also
seems like the easiest path for all of the documentation, scripts, and user
habits out there. I don't mind if the backend package is called "dnf", but
why not keep /usr/bin/yum as the primary command and just do the right
thing, only warning on incompatible usage rather than nagging every time it
is used?

I strongly agree with this for practical reasons.  There is no good rationale for moving away from yum as the name of the command except some of the command line changes which happened with yum anyway (download only was added and later removed for example) and one can warn specifically for those.  The API changes are not something users care about.  Also, dnf needs to drop all the legacy options before the transition (ie)  pick erase or remove (preferably the latter) etc rather than retain all the compatibility options. 

Rahul