{ "content": [ { "type": "text", "text": "# local::lib (perldoc)\n\n## NAME\n\nlocal::lib - create and use a local lib/ for perl modules with PERL5LIB\n\n## SYNOPSIS\n\nIn code -\nuse local::lib; # sets up a local lib at ~/perl5\nuse local::lib '~/foo'; # same, but ~/foo\n# Or...\nuse FindBin;\nuse local::lib \"$FindBin::Bin/../support\"; # app-local support library\nFrom the shell -\n# Install LWP and its missing dependencies to the '~/perl5' directory\nperl -MCPAN -Mlocal::lib -e 'CPAN::install(LWP)'\n# Just print out useful shell commands\n$ perl -Mlocal::lib\nPERLMBOPT='--installbase /home/username/perl5'; export PERLMBOPT;\nPERLMMOPT='INSTALLBASE=/home/username/perl5'; export PERLMMOPT;\nPERL5LIB=\"/home/username/perl5/lib/perl5\"; export PERL5LIB;\nPATH=\"/home/username/perl5/bin:$PATH\"; export PATH;\nPERLLOCALLIBROOT=\"/home/usename/perl5:$PERLLOCALLIBROOT\"; export PERLLOCALLIBROOT;\nFrom a .bashprofile or .bashrc file -\neval \"$(perl -I$HOME/perl5/lib/perl5 -Mlocal::lib)\"\n\n## DESCRIPTION\n\nThis module provides a quick, convenient way of bootstrapping a user-local Perl module library\nlocated within the user's home directory. It also constructs and prints out for the user the\nlist of environment variables using the syntax appropriate for the user's current shell (as\nspecified by the \"SHELL\" environment variable), suitable for directly adding to one's shell\nconfiguration file.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS** (2 subsections)\n- **RATIONALE**\n- **DESCRIPTION**\n- **CREATING A SELF-CONTAINED SET OF MODULES**\n- **IMPORT OPTIONS**\n- **CLASS METHODS**\n- **OBJECT INTERFACE**\n- **ATTRIBUTES**\n- **OBJECT METHODS**\n- **LIMITATIONS**\n- **TROUBLESHOOTING**\n- **ENVIRONMENT**\n- **SEE ALSO**\n- **SUPPORT**\n- **AUTHOR**\n- **CONTRIBUTORS**\n- **COPYRIGHT**\n- **LICENSE**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "local::lib", "section": "", "mode": "perldoc", "summary": "local::lib - create and use a local lib/ for perl modules with PERL5LIB", "synopsis": "In code -\nuse local::lib; # sets up a local lib at ~/perl5\nuse local::lib '~/foo'; # same, but ~/foo\n# Or...\nuse FindBin;\nuse local::lib \"$FindBin::Bin/../support\"; # app-local support library\nFrom the shell -\n# Install LWP and its missing dependencies to the '~/perl5' directory\nperl -MCPAN -Mlocal::lib -e 'CPAN::install(LWP)'\n# Just print out useful shell commands\n$ perl -Mlocal::lib\nPERLMBOPT='--installbase /home/username/perl5'; export PERLMBOPT;\nPERLMMOPT='INSTALLBASE=/home/username/perl5'; export PERLMMOPT;\nPERL5LIB=\"/home/username/perl5/lib/perl5\"; export PERL5LIB;\nPATH=\"/home/username/perl5/bin:$PATH\"; export PATH;\nPERLLOCALLIBROOT=\"/home/usename/perl5:$PERLLOCALLIBROOT\"; export PERLLOCALLIBROOT;\nFrom a .bashprofile or .bashrc file -\neval \"$(perl -I$HOME/perl5/lib/perl5 -Mlocal::lib)\"", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 27, "subsections": [ { "name": "The bootstrapping technique", "lines": 111 }, { "name": "Differences when using this module under Win32", "lines": 26 } ] }, { "name": "RATIONALE", "lines": 17, "subsections": [] }, { "name": "DESCRIPTION", "lines": 23, "subsections": [] }, { "name": "CREATING A SELF-CONTAINED SET OF MODULES", "lines": 4, "subsections": [] }, { "name": "IMPORT OPTIONS", "lines": 25, "subsections": [] }, { "name": "CLASS METHODS", "lines": 94, "subsections": [] }, { "name": "OBJECT INTERFACE", "lines": 7, "subsections": [] }, { "name": "ATTRIBUTES", "lines": 18, "subsections": [] }, { "name": "OBJECT METHODS", "lines": 55, "subsections": [] }, { "name": "LIMITATIONS", "lines": 35, "subsections": [] }, { "name": "TROUBLESHOOTING", "lines": 13, "subsections": [] }, { "name": "ENVIRONMENT", "lines": 7, "subsections": [] }, { "name": "SEE ALSO", "lines": 2, "subsections": [] }, { "name": "SUPPORT", "lines": 4, "subsections": [] }, { "name": "AUTHOR", "lines": 4, "subsections": [] }, { "name": "CONTRIBUTORS", "lines": 35, "subsections": [] }, { "name": "COPYRIGHT", "lines": 2, "subsections": [] }, { "name": "LICENSE", "lines": 3, "subsections": [] } ], "sections": { "NAME": { "content": "local::lib - create and use a local lib/ for perl modules with PERL5LIB\n", "subsections": [] }, "SYNOPSIS": { "content": "In code -\n\nuse local::lib; # sets up a local lib at ~/perl5\n\nuse local::lib '~/foo'; # same, but ~/foo\n\n# Or...\nuse FindBin;\nuse local::lib \"$FindBin::Bin/../support\"; # app-local support library\n\nFrom the shell -\n\n# Install LWP and its missing dependencies to the '~/perl5' directory\nperl -MCPAN -Mlocal::lib -e 'CPAN::install(LWP)'\n\n# Just print out useful shell commands\n$ perl -Mlocal::lib\nPERLMBOPT='--installbase /home/username/perl5'; export PERLMBOPT;\nPERLMMOPT='INSTALLBASE=/home/username/perl5'; export PERLMMOPT;\nPERL5LIB=\"/home/username/perl5/lib/perl5\"; export PERL5LIB;\nPATH=\"/home/username/perl5/bin:$PATH\"; export PATH;\nPERLLOCALLIBROOT=\"/home/usename/perl5:$PERLLOCALLIBROOT\"; export PERLLOCALLIBROOT;\n\nFrom a .bashprofile or .bashrc file -\n\neval \"$(perl -I$HOME/perl5/lib/perl5 -Mlocal::lib)\"\n", "subsections": [ { "name": "The bootstrapping technique", "content": "A typical way to install local::lib is using what is known as the \"bootstrapping\" technique. You\nwould do this if your system administrator hasn't already installed local::lib. In this case,\nyou'll need to install local::lib in your home directory.\n\nEven if you do have administrative privileges, you will still want to set up your environment\nvariables, as discussed in step 4. Without this, you would still install the modules into the\nsystem CPAN installation and also your Perl scripts will not use the lib/ path you bootstrapped\nwith local::lib.\n\nBy default local::lib installs itself and the CPAN modules into ~/perl5.\n\nWindows users must also see \"Differences when using this module under Win32\".\n\n1. Download and unpack the local::lib tarball from CPAN (search for \"Download\" on the CPAN page\nabout local::lib). Do this as an ordinary user, not as root or administrator. Unpack the\nfile in your home directory or in any other convenient location.\n\n2. Run this:\n\nperl Makefile.PL --bootstrap\n\nIf the system asks you whether it should automatically configure as much as possible, you\nwould typically answer yes.\n\n3. Run this: (local::lib assumes you have make installed on your system)\n\nmake test && make install\n\n4. Now we need to setup the appropriate environment variables, so that Perl starts using our\nnewly generated lib/ directory. If you are using bash or any other Bourne shells, you can\nadd this to your shell startup script this way:\n\necho 'eval \"$(perl -I$HOME/perl5/lib/perl5 -Mlocal::lib)\"' >>~/.bashrc\n\nIf you are using C shell, you can do this as follows:\n\n% echo $SHELL\n/bin/csh\n$ echo 'eval `perl -I$HOME/perl5/lib/perl5 -Mlocal::lib`' >> ~/.cshrc\n\nAfter writing your shell configuration file, be sure to re-read it to get the changed\nsettings into your current shell's environment. Bourne shells use \". ~/.bashrc\" for this,\nwhereas C shells use \"source ~/.cshrc\".\n\nBootstrapping into an alternate directory\nIn order to install local::lib into a directory other than the default, you need to specify the\nname of the directory when you call bootstrap. Then, when setting up the environment variables,\nboth perl and local::lib must be told the location of the bootstrap directory. The setup process\nwould look as follows:\n\nperl Makefile.PL --bootstrap=~/foo\nmake test && make install\necho 'eval \"$(perl -I$HOME/foo/lib/perl5 -Mlocal::lib=$HOME/foo)\"' >>~/.bashrc\n. ~/.bashrc\n\nOther bootstrapping options\nIf you're on a slower machine, or are operating under draconian disk space limitations, you can\ndisable the automatic generation of manpages from POD when installing modules by using the\n\"--no-manpages\" argument when bootstrapping:\n\nperl Makefile.PL --bootstrap --no-manpages\n\nTo avoid doing several bootstrap for several Perl module environments on the same account, for\nexample if you use it for several different deployed applications independently, you can use one\nbootstrapped local::lib installation to install modules in different directories directly this\nway:\n\ncd ~/mydir1\nperl -Mlocal::lib=./\neval $(perl -Mlocal::lib=./) ### To set the environment for this shell alone\nprintenv ### You will see that ~/mydir1 is in the PERL5LIB\nperl -MCPAN -e install ... ### whatever modules you want\ncd ../mydir2\n... REPEAT ...\n\nIf you use .bashrc to activate a local::lib automatically, the local::lib will be re-enabled in\nany sub-shells used, overriding adjustments you may have made in the parent shell. To avoid\nthis, you can initialize the local::lib in .bashprofile rather than .bashrc, or protect the\nlocal::lib invocation with a $SHLVL check:\n\n[ $SHLVL -eq 1 ] && eval \"$(perl -I$HOME/perl5/lib/perl5 -Mlocal::lib)\"\n\nIf you are working with several \"local::lib\" environments, you may want to remove some of them\nfrom the current environment without disturbing the others. You can deactivate one environment\nlike this (using bourne sh):\n\neval $(perl -Mlocal::lib=--deactivate,~/path)\n\nwhich will generate and run the commands needed to remove \"~/path\" from your various search\npaths. Whichever environment was activated most recently will remain the target for module\ninstallations. That is, if you activate \"~/pathA\" and then you activate \"~/pathB\", new modules\nyou install will go in \"~/pathB\". If you deactivate \"~/pathB\" then modules will be installed\ninto \"~/pathA\" -- but if you deactivate \"~/pathA\" then they will still be installed in\n\"~/pathB\" because pathB was activated later.\n\nYou can also ask \"local::lib\" to clean itself completely out of the current shell's environment\nwith the \"--deactivate-all\" option. For multiple environments for multiple apps you may need to\ninclude a modified version of the \"use FindBin\" instructions in the \"In code\" sample above. If\nyou did something like the above, you have a set of Perl modules at \"~/mydir1/lib\". If you have\na script at \"~/mydir1/scripts/myscript.pl\", you need to tell it where to find the modules you\ninstalled for it at \"~/mydir1/lib\".\n\nIn \"~/mydir1/scripts/myscript.pl\":\n\nuse strict;\nuse warnings;\nuse local::lib \"$FindBin::Bin/..\"; ### points to ~/mydir1 and local::lib finds lib\nuse lib \"$FindBin::Bin/../lib\"; ### points to ~/mydir1/lib\n\nPut this before any BEGIN { ... } blocks that require the modules you installed.\n" }, { "name": "Differences when using this module under Win32", "content": "To set up the proper environment variables for your current session of \"CMD.exe\", you can use\nthis:\n\nC:\\>perl -Mlocal::lib\nset PERLMBOPT=--installbase C:\\DOCUME~1\\ADMINI~1\\perl5\nset PERLMMOPT=INSTALLBASE=C:\\DOCUME~1\\ADMINI~1\\perl5\nset PERL5LIB=C:\\DOCUME~1\\ADMINI~1\\perl5\\lib\\perl5\nset PATH=C:\\DOCUME~1\\ADMINI~1\\perl5\\bin;%PATH%\n\n### To set the environment for this shell alone\nC:\\>perl -Mlocal::lib > %TEMP%\\tmp.bat && %TEMP%\\tmp.bat && del %TEMP%\\tmp.bat\n### instead of $(perl -Mlocal::lib=./)\n\nIf you want the environment entries to persist, you'll need to add them to the Control Panel's\nSystem applet yourself or use App::local::lib::Win32Helper.\n\nThe \"~\" is translated to the user's profile directory (the directory named for the user under\n\"Documents and Settings\" (Windows XP or earlier) or \"Users\" (Windows Vista or later)) unless\n$ENV{HOME} exists. After that, the home directory is translated to a short name (which means the\ndirectory must exist) and the subdirectories are created.\n\nPowerShell\nlocal::lib also supports PowerShell, and can be used with the \"Invoke-Expression\" cmdlet.\n\nInvoke-Expression \"$(perl -Mlocal::lib)\"\n" } ] }, "RATIONALE": { "content": "The version of a Perl package on your machine is not always the version you need. Obviously, the\nbest thing to do would be to update to the version you need. However, you might be in a\nsituation where you're prevented from doing this. Perhaps you don't have system administrator\nprivileges; or perhaps you are using a package management system such as Debian, and nobody has\nyet gotten around to packaging up the version you need.\n\nlocal::lib solves this problem by allowing you to create your own directory of Perl packages\ndownloaded from CPAN (in a multi-user system, this would typically be within your own home\ndirectory). The existing system Perl installation is not affected; you simply invoke Perl with\nspecial options so that Perl uses the packages in your own local package directory rather than\nthe system packages. local::lib arranges things so that your locally installed version of the\nPerl packages takes precedence over the system installation.\n\nIf you are using a package management system (such as Debian), you don't need to worry about\nDebian and CPAN stepping on each other's toes. Your local version of the packages will be\nwritten to an entirely separate directory from those installed by Debian.\n", "subsections": [] }, "DESCRIPTION": { "content": "This module provides a quick, convenient way of bootstrapping a user-local Perl module library\nlocated within the user's home directory. It also constructs and prints out for the user the\nlist of environment variables using the syntax appropriate for the user's current shell (as\nspecified by the \"SHELL\" environment variable), suitable for directly adding to one's shell\nconfiguration file.\n\nMore generally, local::lib allows for the bootstrapping and usage of a directory containing Perl\nmodules outside of Perl's @INC. This makes it easier to ship an application with an app-specific\ncopy of a Perl module, or collection of modules. Useful in cases like when an upstream\nmaintainer hasn't applied a patch to a module of theirs that you need for your application.\n\nOn import, local::lib sets the following environment variables to appropriate values:\n\nPERLMBOPT\nPERLMMOPT\nPERL5LIB\nPATH\nPERLLOCALLIBROOT\n\nWhen possible, these will be appended to instead of overwritten entirely.\n\nThese values are then available for reference by any code after import.\n", "subsections": [] }, "CREATING A SELF-CONTAINED SET OF MODULES": { "content": "See lib::core::only for one way to do this - but note that there are a number of caveats, and\nthe best approach is always to perform a build against a clean perl (i.e. site and vendor as\nclose to empty as possible).\n", "subsections": [] }, "IMPORT OPTIONS": { "content": "Options are values that can be passed to the \"local::lib\" import besides the directory to use.\nThey are specified as \"use local::lib '--option'[, path];\" or \"perl\n-Mlocal::lib=--option[,path]\".\n\n--deactivate\nRemove the chosen path (or the default path) from the module search paths if it was added by\n\"local::lib\", instead of adding it.\n\n--deactivate-all\nRemove all directories that were added to search paths by \"local::lib\" from the search paths.\n\n--quiet\nDon't output any messages about directories being created.\n\n--always\nAlways add directories to environment variables, ignoring if they are already included.\n\n--shelltype\nSpecify the shell type to use for output. By default, the shell will be detected based on the\nenvironment. Should be one of: \"bourne\", \"csh\", \"cmd\", or \"powershell\".\n\n--no-create\nPrevents \"local::lib\" from creating directories when activating dirs. This is likely to cause\nissues on Win32 systems.\n", "subsections": [] }, "CLASS METHODS": { "content": "ensuredirstructurefor\nArguments: $path\nReturn value: None\n\nAttempts to create a local::lib directory, including subdirectories and all required parent\ndirectories. Throws an exception on failure.\n\nprintenvironmentvarsfor\nArguments: $path\nReturn value: None\n\nPrints to standard output the variables listed above, properly set to use the given path as the\nbase directory.\n\nbuildenvironmentvarsfor\nArguments: $path\nReturn value: %environmentvars\n\nReturns a hash with the variables listed above, properly set to use the given path as the base\ndirectory.\n\nsetupenvhashfor\nArguments: $path\nReturn value: None\n\nConstructs the %ENV keys for the given path, by calling \"buildenvironmentvarsfor\".\n\nactivepaths\nArguments: None\nReturn value: @paths\n\nReturns a list of active \"local::lib\" paths, according to the \"PERLLOCALLIBROOT\" environment\nvariable and verified against what is really in @INC.\n\ninstallbaseperlpath\nArguments: $path\nReturn value: $installbaseperlpath\n\nReturns a path describing where to install the Perl modules for this local library installation.\nAppends the directories \"lib\" and \"perl5\" to the given path.\n\nlibpathsfor\nArguments: $path\nReturn value: @libpaths\n\nReturns the list of paths perl will search for libraries, given a base path. This includes the\nbase path itself, the architecture specific subdirectory, and perl version specific\nsubdirectories. These paths may not all exist.\n\ninstallbasebinpath\nArguments: $path\nReturn value: $installbasebinpath\n\nReturns a path describing where to install the executable programs for this local library\ninstallation. Appends the directory \"bin\" to the given path.\n\ninstalleroptionsfor\nArguments: $path\nReturn value: %installerenvvars\n\nReturns a hash of environment variables that should be set to cause installation into the given\npath.\n\nresolveemptypath\nArguments: $path\nReturn value: $basepath\n\nBuilds and returns the base path into which to set up the local module installation. Defaults to\n\"~/perl5\".\n\nresolvehomepath\nArguments: $path\nReturn value: $homepath\n\nAttempts to find the user's home directory. If no definite answer is available, throws an\nexception.\n\nresolverelativepath\nArguments: $path\nReturn value: $absolutepath\n\nTranslates the given path into an absolute path.\n\nresolvepath\nArguments: $path\nReturn value: $absolutepath\n\nCalls the following in a pipeline, passing the result from the previous to the next, in an\nattempt to find where to configure the environment for a local library installation:\n\"resolveemptypath\", \"resolvehomepath\", \"resolverelativepath\". Passes the given path\nargument to \"resolveemptypath\" which then returns a result that is passed to\n\"resolvehomepath\", which then has its result passed to \"resolverelativepath\". The result of\nthis final call is returned from \"resolvepath\".\n", "subsections": [] }, "OBJECT INTERFACE": { "content": "new\nArguments: %attributes\nReturn value: $locallib\n\nConstructs a new \"local::lib\" object, representing the current state of @INC and the relevant\nenvironment variables.\n", "subsections": [] }, "ATTRIBUTES": { "content": "roots\nAn arrayref representing active \"local::lib\" directories.\n\ninc\nAn arrayref representing @INC.\n\nlibs\nAn arrayref representing the PERL5LIB environment variable.\n\nbins\nAn arrayref representing the PATH environment variable.\n\nextra\nA hashref of extra environment variables (e.g. \"PERLMMOPT\" and \"PERLMBOPT\")\n\nnocreate\nIf set, \"local::lib\" will not try to create directories when activating them.\n", "subsections": [] }, "OBJECT METHODS": { "content": "clone\nArguments: %attributes\nReturn value: $locallib\n\nConstructs a new \"local::lib\" object based on the existing one, overriding the specified\nattributes.\n\nactivate\nArguments: $path\nReturn value: $newlocallib\n\nConstructs a new instance with the specified path active.\n\ndeactivate\nArguments: $path\nReturn value: $newlocallib\n\nConstructs a new instance with the specified path deactivated.\n\ndeactivateall\nArguments: None\nReturn value: $newlocallib\n\nConstructs a new instance with all \"local::lib\" directories deactivated.\n\nenvironmentvarsstring\nArguments: [ $shelltype ]\nReturn value: $shellenvstring\n\nReturns a string to set up the \"local::lib\", meant to be run by a shell.\n\nbuildenvironmentvars\nArguments: None\nReturn value: %environmentvars\n\nReturns a hash with the variables listed above, properly set to use the given path as the base\ndirectory.\n\nsetupenvhash\nArguments: None\nReturn value: None\n\nConstructs the %ENV keys for the given path, by calling \"buildenvironmentvars\".\n\nsetuplocallib\nConstructs the %ENV hash using \"setupenvhash\", and set up @INC.\n\nA WARNING ABOUT UNINST=1\nBe careful about using local::lib in combination with \"make install UNINST=1\". The idea of this\nfeature is that will uninstall an old version of a module before installing a new one. However\nit lacks a safety check that the old version and the new version will go in the same directory.\nUsed in combination with local::lib, you can potentially delete a globally accessible version of\na module while installing the new version in a local place. Only combine \"make install UNINST=1\"\nand local::lib if you understand these possible consequences.\n", "subsections": [] }, "LIMITATIONS": { "content": "* Directory names with spaces in them are not well supported by the perl toolchain and the\nprograms it uses. Pure-perl distributions should support spaces, but problems are more\nlikely with dists that require compilation. A workaround you can do is moving your\nlocal::lib to a directory with spaces after you installed all modules inside your local::lib\nbootstrap. But be aware that you can't update or install CPAN modules after the move.\n\n* Rather basic shell detection. Right now anything with csh in its name is assumed to be a C\nshell or something compatible, and everything else is assumed to be Bourne, except on Win32\nsystems. If the \"SHELL\" environment variable is not set, a Bourne-compatible shell is\nassumed.\n\n* Kills any existing PERLMMOPT or PERLMBOPT.\n\n* Should probably auto-fixup CPAN config if not already done.\n\n* On VMS and MacOS Classic (pre-OS X), local::lib loads File::Spec. This means any File::Spec\nversion installed in the local::lib will be ignored by scripts using local::lib. A\nworkaround for this is using \"use lib \"$locallib/lib/perl5\";\" instead of using \"local::lib\"\ndirectly.\n\n* Conflicts with ExtUtils::MakeMaker's \"PREFIX\" option. \"local::lib\" uses the \"INSTALLBASE\"\noption, as it has more predictable and sane behavior. If something attempts to use the\n\"PREFIX\" option when running a Makefile.PL, ExtUtils::MakeMaker will refuse to run, as the\ntwo options conflict. This can be worked around by temporarily unsetting the \"PERLMMOPT\"\nenvironment variable.\n\n* Conflicts with Module::Build's \"--prefix\" option. Similar to the previous limitation, but\nany \"--prefix\" option specified will be ignored. This can be worked around by temporarily\nunsetting the \"PERLMBOPT\" environment variable.\n\nPatches very much welcome for any of the above.\n\n* On Win32 systems, does not have a way to write the created environment variables to the\nregistry, so that they can persist through a reboot.\n", "subsections": [] }, "TROUBLESHOOTING": { "content": "If you've configured local::lib to install CPAN modules somewhere in to your home directory, and\nat some point later you try to install a module with \"cpan -i Foo::Bar\", but it fails with an\nerror like: \"Warning: You do not have permissions to install into\n/usr/lib64/perl5/siteperl/5.8.8/x8664-linux at /usr/lib64/perl5/5.8.8/Foo/Bar.pm\" and buried\nwithin the install log is an error saying \"'INSTALLBASE' is not a known MakeMaker parameter\nname\", then you've somehow lost your updated ExtUtils::MakeMaker module.\n\nTo remedy this situation, rerun the bootstrapping procedure documented above.\n\nThen, run \"rm -r ~/.cpan/build/Foo-Bar*\"\n\nFinally, re-run \"cpan -i Foo::Bar\" and it should install without problems.\n", "subsections": [] }, "ENVIRONMENT": { "content": "SHELL\nCOMSPEC\nlocal::lib looks at the user's \"SHELL\" environment variable when printing out commands to\nadd to the shell configuration file.\n\nOn Win32 systems, \"COMSPEC\" is also examined.\n", "subsections": [] }, "SEE ALSO": { "content": "* Perl Advent article, 2011 \n", "subsections": [] }, "SUPPORT": { "content": "IRC:\n\nJoin #toolchain on irc.perl.org.\n", "subsections": [] }, "AUTHOR": { "content": "Matt S Trout http://www.shadowcat.co.uk/\n\nautoinstall fixes kindly sponsored by http://www.takkle.com/\n", "subsections": [] }, "CONTRIBUTORS": { "content": "Patches to correctly output commands for csh style shells, as well as some documentation\nadditions, contributed by Christopher Nehren .\n\nDoc patches for a custom local::lib directory, more cleanups in the english documentation and a\ngerman documentation contributed by Torsten Raudssus .\n\nHans Dieter Pearcey sent in some additional tests for ensuring things will\ninstall properly, submitted a fix for the bug causing problems with writing Makefiles during\nbootstrapping, contributed an example program, and submitted yet another fix to ensure that\nlocal::lib can install and bootstrap properly. Many, many thanks!\n\npattern of Freenode IRC contributed the beginnings of the Troubleshooting section. Many thanks!\n\nPatch to add Win32 support contributed by Curtis Jewell .\n\nWarnings for missing PATH/PERL5LIB (as when not running interactively) silenced by a patch from\nMarco Emilio Poleggi.\n\nMark Stosberg provided the code for the now deleted '--self-contained'\noption.\n\nDocumentation patches to make win32 usage clearer by David Mertens \n(run4flat).\n\nBrazilian portuguese translation and minor doc patches contributed by Breno G. de Oliveira\n.\n\nImprovements to stacking multiple local::lib dirs and removing them from the environment later\non contributed by Andrew Rodland .\n\nPatch for Carp version mismatch contributed by Hakim Cassimally .\n\nRewrite of internals and numerous bug fixes and added features contributed by Graham Knop\n.\n", "subsections": [] }, "COPYRIGHT": { "content": "Copyright (c) 2007 - 2013 the local::lib \"AUTHOR\" and \"CONTRIBUTORS\" as listed above.\n", "subsections": [] }, "LICENSE": { "content": "This is free software; you can redistribute it and/or modify it under the same terms as the Perl\n5 programming language system itself.\n", "subsections": [] } } } }