I use Module :: Build (although I am flexible in build environments) to package some perl software that I write for internal use, where I work. It includes several scripts and some auxiliary modules. My plan is to make sure that during the build process you can specify the prefix of what you want (i.e., something outside perl default @INC), and the built-in scripts should still find their auxiliary modules without any problems .
I want to do this because I want to distribute this software internally using "Encap", which is a packaging tool that by default cannot install anything outside of / usr / local and reside on RedHat, our perl does not look for / usr / local / lib for default modules.
This leaves me the opportunity to either tell the user to manually install PERL5LIBin / usr / local / lib every time they want to run the application, or do something smart with the build system so that it will script every line of the script use libafter the instruction --prefix.
Right now I just set the use libdirect pointing to / usr / local / lib manually in each of my scripts, but I donโt really like this as a solution. Mainly due to the testing process: I want to override @INCduring testing to first use my working directory for perl modules, but when creating it, the working directory should be removed from @INCand replaced with the user-specified prefix, But also because I would like to so that this software is installed in arbitrary places (for example, its own small island somewhere in NFS with its own bin / and lib / dirs) and still without problems.
Question :
:: Build use lib ? , MakeMaker pm_filter, , .pm , .pm , . :: Build , , , .