On Tue, Nov 11, 2003 at 04:18:08PM -0600, Dave Rolsky wrote: > > As I understand (or misunderstand) FHS everything that is sharable between > > machines is supposed to go in /usr/share/whatever. So perl modules that > > get interpreted by the perl binary can go in share I guess. > > But P::V has a compiled component as well. So it's not all shareable.
I don't really know what the context of this discussion is, but MakeMaker doesn't split distributions into "architecture specific" and "architecture independent". If one part of the distribution is arch dependent, it all goes into the architecture directories. Even the pure Perl parts. This is the simplest and safest thing to do. As for the FHS (I assume you mean this: http://www.pathname.com/fhs/), MakeMaker is archtecture independent (this means non-Unix, too) and not bound by it. Its up to the vendor to configure their Perl to match the FHS should they desire. Is MakeMaker's behavior violating the FHS? I honestly don't care. But since you asked, it appears the answer is no. FHS 2.2 Section 4.7.1 Paragraph 2 Applications may use a single subdirectory under /usr/lib. If an application uses a subdirectory, all architecture-dependent data exclusively used by the application must be placed within that subdirectory.[footnote 19] Footnote 19 [19] For example, the perl5 subdirectory for Perl 5 modules and libraries. Thus Debian's current Perl policy of putting arch independent perl modules into /usr/lib/perl5 and arch dependent stuff in /usr/share/perl5 is in violation of the FHS. This may be for historical reasons. Anyhow, blissfully not my problem. :) -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/ I knew right away that my sock and your eyebrows could be best friends.
