-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Philipp Thomas wrote: > On Wed, 11 Jan 2006 18:37:40 -0500, Yu Safin wrote: > >> 1) I am not clear as to why some rpm's are named i386 and some noarch. > > Every perl module that either has architecture dependent parts or > somehow depends on a given architecture will be built for all supported > architectures. Those perl modules that really are architecture > independent (i.e. only consist of perl code) get marked noarch in the > rpm spec file and will be built once for all architectures. > > If you find perl modules that aren't marked noarch but seem to work on > other architectures as well, feel free to report them in > https://bugzilla.novell.com .
Well, actually there's some trickery with Perl modules. Even the Perl modules that are architecture-independent (because they only contain Perl code, and no shared library/PIC object file) are _NOT_ noarch RPMs. The reason is that Perl modules are installed under /usr/lib/perl5/... So what? On 64bit, that directory is /usr/lib64/perl5/... And... ? If RPMs with Perl modules were "noarch", then they could not be built - - once for 32bit, with the prefix /usr/lib/perl5/ - - once for 64bit, with the prefix /usr/lib64/perl5/ Installing a Perl module into /usr/lib/perl5 on a 64bit SUSE Linux won't work unless you hack Perl's search path, because perl expects the module to be under /usr/lib64/perl5 Hope this clarifies ;) BTW, same goes for Python modules. cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDxgQRr3NMWliFcXcRAoN3AJ9SUctyto/iMhrulDID5y26GNypDgCgmfbM cu7efSPSCh3zZERwhSg11CI= =UzYW -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
