Re: F22 System Wide Change: Replace Yum With DNF

[Jamie Duncan <jduncan@xxxxxxxxxx>]

I am +1 for keeping the 'yum' name for the new manager, if only for the connotation.

Telling users/consumers/customers that yum is upgraded and awesome is much easier than telling them that yum has been replaced and that the new tool is awesome.

Even something like 'yum4' would be preferable to a new acronym to learn.

Thanks,

Jamie Duncan, RHCE
Senior Technical Account Manager
Red Hat, Inc.

jduncan@xxxxxxxxxx

w-804.343.6086
c-804.307.7079
tech support-888.GO.REDHAT

---

From: "Rahul Sundaram" <metherid@xxxxxxxxx>
To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, June 12, 2014 11:03:35 AM
Subject: Re: F22 System Wide Change: Replace Yum With DNF

Hi

On Thu, Jun 12, 2014 at 10:29 AM, Jan Zelený  wrote:

We are on the same page, thanks for your input.

I don't think so.  You are clearly arguing for a temporary compatibility wrapper but eventually forcing everyone to use dnf as the command.  The other side is wanting yum to continue to remain the name for the command with yum-legacy for temporary transition.  In otherwords, dnf is an internal project name and doesn't need to be exposed to the user.  The analogy to systemctl doesn't work because systemctl is part of a completely separate project that works very differently from service command while dnf is a experimental fork of yum with a few fairly minor differences in command line and configuration options.

Rahul

--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct