On Thu, Sep 12, 2013 at 12:58:43PM +0100, Adam Spiers wrote:
It seems that currently my .spec results in the package containing files such as:
/usr/lib/perl5/vendor_perl/5.18.1/Stow.pm
which will only be found by the default @INC of a perl-5.18.1 package.
(It will also be found by perl-5.18.2 and so on.)
However, I know for a fact that my non-binary modules will work with *any* Perl >= 5.6.1, and so would prefer to install them to a non-versioned directory, e.g.
$ perl -V:vendorlib_stem vendorlib_stem='/usr/lib/perl5/vendor_perl';
However this is not on the default @INC.
Well, completely unversioned is a bit frowned upon. There are incompatible changes between the major perl versions, and how will you know that perl-5.20 does not break your module?
In contrast, sitelib_stem does seem to be, although my understanding is that "vendor" packages such as those from OBS should install to vendor* paths rather than site*.
sitelib_stem is there because some people really want to have versionless modules locally.
Is there a good reason for vendorlib_stem not being on @INC, and if so, is it OK for me to install to sitelib_stem instead?
I consider it bad style, IMHO sitelib is a place where local admins can install stuff, e.g. by directly calling the cpan tool. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org