[Yum] yum and multi architectures ???

seth vidal skvidal at phy.duke.edu
Tue Feb 18 22:07:45 UTC 2003


> > > is this the only place to add it ?
> > 
> > it would seem more effective to use some variant on:
> > 
> >    grep ^arch_compa /usr/lib/rpm/rpmrc
> > 

ok, so looking at this some more.

A sample from that output:
arch_compat: alphaev67: alphaev6
arch_compat: alphaev6: alphapca56
arch_compat: alphapca56: alphaev56
arch_compat: alphaev56: alphaev5
arch_compat: alphaev5: alpha
arch_compat: alpha: axp noarch
arch_compat: athlon: i686
arch_compat: i686: i586
arch_compat: i586: i486
arch_compat: i486: i386
arch_compat: i386: noarch


Now is it reasonable to read that as:

alphaev67 compat w/ alphaev6
alphaev6 compat w/ alphaca56

and are they therefore transitive?

is alphaev67 compat with alphaev6?

I would say yes based on what the athlon -> i386 say.

And if that's true can I look through this list, grab things where the
line ends in noarch and call those the "base classes" - doing a quick
grep of the one on my system that gets me: 
 alpha
 i386
 rs6000
 sparc
 mips
 mipsel
 parisc
 armv4b
 armv3l
 atarist
 atariste
 ataritt
 falcon
 atariclone
 milan
 hades
 i370
 s390
 s390x
 ia64
 x86_64


but then there is ppc and ppc64 which appear to not support noarch
packages. Is that an endian issue?

-sv

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.baseurl.org/pipermail/yum/attachments/20030218/610c30e6/attachment-0001.pgp 


More information about the Yum mailing list