On Tue, Dec 07, 2004 at 10:50:49AM -0500, seth vidal wrote: > On Tue, 2004-12-07 at 16:48 +0100, Axel Thimm wrote: > > On Tue, Dec 07, 2004 at 10:40:17AM -0500, seth vidal wrote: > > > > The typical use should not include choosing archs at all. Currently > > > > yum bundles by default i386 packages to x86_64 ones. So even a > > > > non-multilib "native" [1] system becomes multilib on the first yum > > > > upgrade ... > > > > > > > > [1] All but grub.i386 > > > > > > Boy, glad that won't cause any ambiguity. > > > > What do you mean? The above describes _current_ yum behaviour. > > I was replying to do the: > this should be consistent, except for grub, comment. > > it's just ironic. No, it's not, you did not understand the above: o The system is non-multilib, i.e. there are no double packages existing for different archs. o The system is almost native, the only non-x86_64 package is grub. That's why non-multilib is not in quotes, while native was. Anyway the system becomes multi-lib the moment I use yum ... -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.dulug.duke.edu/pipermail/yum/attachments/20041207/86cdb4f7/attachment.bin
