FAQ 8.47 How do I keep my own module/library directory?
in [Perl]
|
Prev: FAQ 8.13 How do I trap control characters/signals?
Next: FAQ 4.54 Why does defined() return true on empty arrays and hashes?
From: PerlFAQ Server on 16 Jun 2010 18:00 This is an excerpt from the latest version perlfaq8.pod, which comes with the standard Perl distribution. These postings aim to reduce the number of repeated questions as well as allow the community to review and update the answers. The latest version of the complete perlfaq is at http://faq.perl.org . -------------------------------------------------------------------- 8.47: How do I keep my own module/library directory? When you build modules, tell Perl where to install the modules. For "Makefile.PL"-based distributions, use the INSTALL_BASE option when generating Makefiles: perl Makefile.PL INSTALL_BASE=/mydir/perl You can set this in your "CPAN.pm" configuration so modules automatically install in your private library directory when you use the CPAN.pm shell: % cpan cpan> o conf makepl_arg INSTALL_BASE=/mydir/perl cpan> o conf commit For "Build.PL"-based distributions, use the --install_base option: perl Build.PL --install_base /mydir/perl You can configure "CPAN.pm" to automatically use this option too: % cpan cpan> o conf mbuild_arg "--install_base /mydir/perl" cpan> o conf commit INSTALL_BASE tells these tools to put your modules into /mydir/perl/lib/perl5. See "How do I add a directory to my include path (@INC) at runtime?" for details on how to run your newly installed modules. There is one caveat with INSTALL_BASE, though, since it acts differently than the PREFIX and LIB settings that older versions of "ExtUtils::MakeMaker" advocated. INSTALL_BASE does not support installing modules for multiple versions of Perl or different architectures under the same directory. You should consider if you really want that , and if you do, use the older PREFIX and LIB settings. See the "ExtUtils::Makemaker" documentation for more details. -------------------------------------------------------------------- The perlfaq-workers, a group of volunteers, maintain the perlfaq. They are not necessarily experts in every domain where Perl might show up, so please include as much information as possible and relevant in any corrections. The perlfaq-workers also don't have access to every operating system or platform, so please include relevant details for corrections to examples that do not work on particular platforms. Working code is greatly appreciated. If you'd like to help maintain the perlfaq, see the details in perlfaq.pod.
From: Ben Morrow on 16 Jun 2010 18:41 Quoth PerlFAQ Server <brian(a)theperlreview.com>: > > 8.47: How do I keep my own module/library directory? Should this answer mention local::lib? I believe it's considered best practice nowadays for keeping a local module directory. Ben
From: Chris Nehren on 16 Jun 2010 21:14 On 2010-06-16, Ben Morrow scribbled these curious markings: > > Quoth PerlFAQ Server <brian(a)theperlreview.com>: >> >> 8.47: How do I keep my own module/library directory? > > Should this answer mention local::lib? I believe it's considered best > practice nowadays for keeping a local module directory. Yes. Not that a current maintainer of the module would be biased at all, of course... -- Thanks and best regards, Chris Nehren Unless noted, all content I post is CC-BY-SA.
From: brian d foy on 17 Jun 2010 13:04
In article <mh0oe7-qmn.ln1(a)osiris.mauzo.dyndns.org>, Ben Morrow <ben(a)morrow.me.uk> wrote: > Quoth PerlFAQ Server <brian(a)theperlreview.com>: > > > > 8.47: How do I keep my own module/library directory? > > Should this answer mention local::lib? Yes it should. I'll look into this. Thanks, |