-----Original Message----- From: Hans Deragon [mailto:hans@deragon.biz] Sent: Tue, August 12, 2003 3:37 PM To: rhl-beta-list@redhat.com Subject: APT, Yum and Red Carpet
Is apt going to make it, or just yum? (Or, in other words,
am I really
gonna have to break down and learn yum?)
IMHO, we should stick with one upgrade system only. Lets take the best and support it. The last thing I want is a community with full of repositories, half apt and half yum. Its time to make a standard for package distribution within Red Hat and we should use one system wisely. I do not care which one it is, as long as it is the best.
It would be very couterproductive for my grandma to have to use apt for installing one appl, and yum for installing another. Imagine that she has to first browse the list of apps available through apt, do not find the software and then browse through the list of apps on yum. Not very intuitive. Not the way to go. This is one case where competition is not welcomed, but a standard is.
I found yum to be much slower comparing to apt. On the other hand, apt sometimes finds some non-existing dependancies, and wants to remove some packages, when is not required.
Pavel.
Quoting Pavel Rozenboim pavelr@coresma.com:
I found yum to be much slower comparing to apt. On the other hand, apt sometimes finds some non-existing dependancies, and wants to remove some packages, when is not required.
No, apt doesn't imagine up dependencies, the difference comes from the fact that apt requires rpmdb consistency at all times, others don't care as long as the transaction at hand gets it dependencies satisfied.
Suppose you have libfoo and libfoo-devel installed. Do "rpm -e --nodeps libfoo" and try to install something unrelated. Apt will refuse to do anything unless you fix the libfoo-devel -> libfoo dependency first, or the dependency will be fixed as part of the next operation. Yum, anaconda and up2date wont care.