Alan Burlison is the perl maintainer for Solaris; he's best equipped to answer your questions (this alias really isn't the right place for it, but I can't think of a particularly good one). I know he rarely has time to answer email, so I'll do my best, and he can correct me if I'm wrong.
On Mon, Sep 08, 2008 at 05:24:28PM +0200, Alexander Vlasov wrote: > While trying to package some useful Perl modules I found out that it's > absolutely unclear how filesystem layout should look like. > Quick look at /usr/perl revealed that few possibilities exists: > > 1. 5.8.4/lib hierarchy. > 2. 5.8.4/lib/i86pc-solaris-64int hierarchy > 3. site_perl/5.8.4/i86pc-solaris-64int hierarchy > 4. vendor_perl/5.8.4/i86pc-solaris-64int hierarchy > > so the questions are: > 1. what the point of i86pc-solaris-64int sub-hier in 5.8.4/lib (and > site_perl/5.8.4 and vendor_perl/5.8.4)? First guess was `dependency on > some binary stuff', but that's seems to be wrong. I think that's just the way that perl installs itself naturally, and it's probably easier a) not to fight it and b) be like all the other perl installations in the world. > 2. what the difference between $VERSION/lib, site_per/$VERSION (note: no > lib/) and vendor_perl/$VERSION (once again no lib/)? $VERSION/lib is the place where the modules distributed with core perl are installed. vendor_perl (like vendor-packages in our Python install) is where the distribution vendor (like Sun) gets to put stuff. And site_perl (and site-packages for Python) is where the end-user puts their own things. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
