On Wed, 16 May 2007, Marcus Rueckert wrote: > On 2007-05-16 13:35:58 +0200, Richard Guenther wrote: > > On Wed, 16 May 2007, Marcus Rueckert wrote: > > > > > On 2007-05-16 11:40:13 +0200, Michal Marek wrote: > > > > Actually unlike python, the perl directory layout doesn't prevent you > > > > from creating noarch packages, because it's /usr/lib/perl5 everywhere > > > > and the arch-dependent files go to /usr/lib/perl5/$arch-$os-blah-blah. > > > > Just there aren't many (read: zero) noarch perl packages in the > > > > distribution :-) > > > > > > there are zero python noarch aswell. and zero ruby noarch. > > > e.g. ruby could do the same as perl. always install into /usr/lib. the > > > arch dependent part is encapsulated in a subdir. > > > > > > vendordir: /usr/lib64/ruby/vendor_ruby > > > vendorlibdir: /usr/lib64/ruby/vendor_ruby/1.8 > > > vendorarchdir: /usr/lib64/ruby/vendor_ruby/1.8/x86_64-linux > > > > Architecture independent files must go in /usr/share > > thats the theory. now lets see the practice.
If you change something there's no need to not follow the "theory". Richard. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
