F22 System Wide Change: Replace Yum With DNF

[Petr Spacek]

On 13.6.2014 14:58, Reindl Harald wrote:
>
> Am 13.06.2014 14:53, schrieb Jan Zelený:
>> That being said, the reason for not renaming dnf to yum is that renaming this
>> project to yum will do nothing else than to confuse its users, as they will
>> think this is still yum and they should expect from dnf it what they expected
>> from yum. They should not. And dnf is not yum, I'm really sorry if you think
>> it is.
>
> the user expects that anyways if you replace something he
> did not asked for replace it and what just worked for him
>
> why do so many developers not understand that simple fact?

I don't think that simple fact that DNF is re-write of YUM justifies re-naming 
and re-training all users. Users don't care what you do with the source. And 
of course, users will complain no matter what you do.

Look at tradition of BIND:
- BIND 4 was the original version (AFAIK)
- BIND 8 was complete re-write of v4
- BIND 9 was complete re-write of v8
- BIND 10 was another attempt to completely re-write it ...

Also, GNOME 3 and KDE 4 were mentioned several times.

IMHO keeping almost-compatible command "yum" forever is priceless.

Re-training all users to use different command is way more intrusive than 
simple fact that some "options" are missing in later version of software.

Users have to deal with it anyway because 100 % backwards compatibility is 
often just an illusion.

-- 
Petr^2 Spacek