| |||||||||||||
Please, Yum Yum!Please, Yum Yum!Posted Jul 9, 2006 17:53 UTC (Sun) by fergal (subscriber, #602)In reply to: Please, Yum Yum! by warmcat1 Parent article: Interview: Jim Gettys (Part II)
> allows cool features like arbitrary mixing and matching with localinstall
apt does this just fine.
> I got the impression apt worked on a more
I'm not so sure, the effect is the same anyway, all the useful repo data is vailable locally. Adding a new package does not cause apt to refetch the entire database for tha repo. I'm not so sure about yum.
> Yum does multiarch/multilib (eg, x86_64 mixing/duping i386 libs) in a
I don't know for sure but neither yum nor apt should know anything about 32 vs 64 bit. There might be some support in rpm or dpkg for a difference but it seems more likely that this is a debian vs fedora filesystem layout difference.
(Log in to post comments)
Please, Yum Yum! Posted Jul 9, 2006 18:08 UTC (Sun) by warmcat1 (guest, #31975) [Link] > apt does this just fine.
Oh well, more props to apt then.
> Adding a new package does not cause apt to
I believe the database part of the repo is lighter in the Yum way of doing things, since it goes to the actual packages to get the full metadata.
> There might be some support in rpm or dpkg for a
Yes, the RPM libs know about multiarch and deal with it, but yum has to be aware of what is going on. For example:
# rpm -qa --queryformat "%{NAME}-%{VERSION}-%{ARCH}\n" | grep glibc
There are two packages called "glibc" of the same version installed in the one box, for example... yum or whatever has to be aware that only the one matching the arch of a new package is a resolution for it, that the -devel package only matches the package with the same arch, etc. Put another way you can have the x86_64 set of libs needed by a package, but if that package is coming in as i686 it is NOT a resolution. Thinking about it the complaints I heard were probably specific to the RPM port of apt and may not say anything about apt's native multiarch powers.
|
|||||||||||||