Steve Langasek <[EMAIL PROTECTED]> writes: > On Sat, Jul 30, 2005 at 12:00:32PM +0200, Marc 'HE' Brockschmidt wrote: >> Ola Lundqvist <[EMAIL PROTECTED]> writes: >>> It is not very different from perl, python, emacs, java (and more) packages >>> that have a "filesystem" of it's own and managed there. >> Listing Perl, Python and Emacs here is totally wrong (and I don't know >> enough about Java packaging to speak about it). Perl is the best >> example: Architecture-dependend data is stored in /usr/lib/perl{/,5/}, >> arch-indep data in /usr/share/perl. > Not 100% true; /usr/lib/perl{/,5/} contain architecture-dependent binary > modules, *along with any architecture-independent wrappers that accompany > them*.
Yes, because the wrappers *need* to fit to version of the compiled binary modules, as everything else could break. This couldn't be ensured if they were put in /usr/share, which is still sometimes managed centrally for a larger number of computers (with different archs). [Note: Version doesn't mean something like 1.2.3 here, but also covers configure-time changes] Marc -- BOFH #153: Big to little endian conversion error
pgpTG0yCCie3i.pgp
Description: PGP signature