I'd like to use Module::Starter to create the basic files for writing modules and I'd like to use the module sthus created while they're still in development, eg. right from their respective blib/ directories.
Problem is, my application can't find them. I have a new module (not created with Module-Starter) just one up directory away and there's no problem in finding it, but the one in blib/ cannot be found.
Here's what I do:
The directories:
~/Devel/Perl/ModuleDevel/ProjectConfig/ProjectConfig.pm
~/Devel/Perl/ModuleDevel/Some-Utils-Text/blib/lib/Some/Utils/Text.pm
The application:
use lib "$ENV{HOME}/Devel/Perl/ModulesDevel/";
use ProjectConfig;
use Some::Utils::Text;
The ProjectConfig module is found and used all right, but not the other. I tried ExtUtils::testlib; as shown in Perl's documentation, but to no avail.
Is it possible at all to work with a module still under development in a blib/ directory and if so, how ?
UPDATE
There was an error: ProjectConfig.pm was still in the application's directory, so it was always found. I removed it and both modules were not found. Good.
To be able to use them at their own location I now do, in the main app:
use lib "$ENV{HOME}/Devel/Perl/ModulesDevel/ProjectConfig/"; use lib "$ENV{HOME}/Devel/Perl/ModulesDevel/Some-Utils-Text/blib/lib/S +ome/Utils/";
Certainly not the most graceful solution, but it works and I can use Module::Starter.
In reply to Module-Starter in development by carcassonne
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |