Details Of DNF Succeeding Yum In Fedora 22 Still Being Discussed

[RahulSundaram]

tell me with you right hand on your heart that rpm isn't crap and i'll never mention it in my postings.

I have been using and maintaining 100's of RPM packages for well over a decade and it servers its purpose very well. If you post about something, it would be helpful if you have an understanding about it but that isn't a requirement of course.

[edmon]

1) Upgrades have nothing to do with package format.
2) If you claim rpm has only two "package managers", you have no clue what you are talking about
3) The profile info is incorrect and Phoronix refuses to update it. Not my problem.

tell me with you right hand on your heart that rpm isn't crap and i'll never mention it in my postings.

[RahulSundaram]

It is 2015 and for all rpm based distributions it is still problem to upgrade from one release to next one without some magic!
It is obvious package type problem if no one can achieve it.
It is easy to write package manager for dpkg this is why there is so many of them and only two for rpm.

And it is very ugly when under your name is written for whom you work and to start talk about other distributions. this seems to be your company PR problem

1) Upgrades have nothing to do with package format.
2) If you claim rpm has only two "package managers", you have no clue what you are talking about
3) The profile info is incorrect and Phoronix refuses to update it. Not my problem.

[edmon]

dnf is a fork of yum. Forked to become the NEXT VERSION of yum. It is not something entirely new.
yum isn't a replacement for rpm. yum is a COMPANION for rpm. A companion that handles repositories of packages and automatically solving conflicts and performing updates.

rpm is for this... and yum is for that ... and dnf is for this.... we all know that.
i just tried to remember what was used to update redhat derivates but didn't remember. now i can it was something like urpmi, another useless crap

[edmon]

There is apt, aptitude, smart, cupt, wajig and so on, it is clearly a problem with that package format as well, right?

It is 2015 and for all rpm based distributions it is still problem to upgrade from one release to next one without some magic!
It is obvious package type problem if no one can achieve it.
It is easy to write package manager for dpkg this is why there is so many of them and only two for rpm.

And it is very ugly when under your name is written for whom you work and to start talk about other distributions. this seems to be your company PR problem

[droidhacker]

After rpm , yum and now dnf it is obvious that the problem is not the package manager but the package type itself.

dnf is a fork of yum. Forked to become the NEXT VERSION of yum. It is not something entirely new.
yum isn't a replacement for rpm. yum is a COMPANION for rpm. A companion that handles repositories of packages and automatically solving conflicts and performing updates.

[droidhacker]

DNF never stood for "Did Not Finish." I get that its used in other circles as standing for that, but I never saw the name "DNF" and thought "did not finish." They probably haven't switched it to be 'yum' because of compatibility concerns where DNF changed functionality / output and if an old script calls the new DNF-ized yum it'll fail and no one will know why.

The fedora wiki specifically refers to it as "nonsense", and the only reference to it IS "did not finish", therefore conclude whatever you like.

Regardless, the original intention remains the same.

Can't imagine why you think that nobody would know why an old script fails. And it isn't like replacing yum with a bash script that calls dnf would solve that anyway.

Content of the current 'yum' command:

executable="/usr/bin/dnf"
msg="Yum command has been deprecated, use dnf instead.\n"\
"See 'man dnf' and 'man yum2dnf' for more information.\n"\
"To transfer transaction metadata from yum to DNF, run 'dnf migrate'"\
"Redirecting to '$executable $@'\n"
echo -e $msg >&2
exec $executable "$@"

[Ericg]

WTF???

DNF was a *nonsense* name given to a FORK of YUM so that the packages would not conflict if both were installed on the same system. The *PLAN* was supposed to be to resume use of the name YUM once it became no longer necessary for the two to be able to coexist. The name DNF is/was supposed to DIE.


DNF: Did Not Finish.
Its finished now, so that does not apply.

DNF never stood for "Did Not Finish." I get that its used in other circles as standing for that, but I never saw the name "DNF" and thought "did not finish." They probably haven't switched it to be 'yum' because of compatibility concerns where DNF changed functionality / output and if an old script calls the new DNF-ized yum it'll fail and no one will know why.

[finalzone]

After rpm , yum and now dnf it is obvious that the problem is not the package manager but the package type itself.

It is like saying in Debian based system

After dpkg , apt-get and now aptitude it is obvious that the problem is not the package manager but the package type itself.

Apply the same logic on other source based distributions and see how that sentence is silly.Now back to the topic.

[droidhacker]

WTF???

DNF was a *nonsense* name given to a FORK of YUM so that the packages would not conflict if both were installed on the same system. The *PLAN* was supposed to be to resume use of the name YUM once it became no longer necessary for the two to be able to coexist. The name DNF is/was supposed to DIE.


DNF: Did Not Finish.
Its finished now, so that does not apply.