Shawn Walker wrote:
Brian Utterback wrote:
Shawn Walker wrote:
If those modules install under /usr/lib/*, yes. If you can have CPAN
install and deliver those modules under /usr/local/perl5 ... or
perhaps /opt/perl5/locl or some other directory that doesn't belong
to an existing package, then you should be ok.
Isn't the whole purpose of the site_perl directory to act as a place
to install locally created perl modules? Is there another directory that
If it is, you'll find a few packages that incorrectly deliver to
site_perl by default, such as:
pkg:/[email protected]
The package system doesn't yet have a concept of package delivered
directories that aren't managed by the package. If a package delivers a
specific directory, then it expects the package manifest to dictate what
the contents of that directory can be. This allows it to deal with fun
things like directories moving to a different location or becoming a
symlink, hardlink, etc.
perl will look in by default that isn't delivered via an IPS pkg?
$ perl -le "$,=', '; print @INC"
...will show you the default search path. From the looks of it, all of
the directories that the default configuration (determined at compile
time) looks in are delivered via the package.
You can also control this through various environment variables and
other methods of course.
Cheers,
So, it looks like a bit of a disconnect. I looked around and it is
definitely the case that site_perl is expected to be used by modules
installed by the local admin in the same way /usr/local mimics /usr.
Apparently CPAN builds modules to go there by default for just this
reason.
In fact, there appears to be mention of this in PSARC 2005/555 "
Python 'vendor-packages' support" where a vendor-packages directory is
added to Python because the pre-existing site-packages is
inappropriate by analogy with the Perl site_perl and vendor_perl
directories.
It would seem that either site_perl should be a symlink to
/usr/local/perl5.../site_perl, or /usr/local/perl5.../site_perl needs
to be added to the default search list in Perl, or pkg needs to be
taught that a package owned by a directory might contain things not
installed by a package. Or CPAN needs to be taught to make IPS
packages. Or maybe all of the above. And those IPS packages that
already deliver to site_perl should be fixed to deliver to vendor_perl.
Is there anyway to get a list of packages that deliver to site_perl
out of pkg?
--
blu
It's bad civic hygiene to build technologies that could someday be
used to facilitate a police state. - Bruce Schneier
----------------------------------------------------------------------
Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom
_______________________________________________
opensolaris-discuss mailing list
[email protected]
