G'day mldvx4,
[In the following, to avoid wrapping, I replaced /home/ken/perl5/perlbrew/perls/perl-5.36.0 with just /PB.]
All of my modules are in one of these directories:
$ perl -E 'say for @INC' /PB/lib/site_perl/5.36.0/cygwin-thread-multi /PB/lib/site_perl/5.36.0 /PB/lib/5.36.0/cygwin-thread-multi /PB/lib/5.36.0
If you run that command, you should get a similar list. Unless you're running Cygwin, you won't have "cygwin-thread-multi". You may additionally have paths with "vendor". The point being that I have all of my modules in @INC directories; not doing this means repeatedly having to add use lib ... statements to many scripts.
To achieve this, I just run the standard incantation:
perl Makefile.PL make make test make install
I let Perl add the module code in appropriate places and don't have to think about it any further.
There are a variety of other ways to do this. These seem to be popular, although I don't use them: Module::Build and local::lib.
So, my recommendation would be to pick a method for installing your modules and use it consistently. Let Perl do most of the work for you. :-)
I've no idea how you develop your modules. If you're doing all the work manually, you may want to look at automating some of it (again, letting Perl work for you). You might want to ask about that separately.
— Ken
In reply to Re: Placement of custom modules outside of home directory?
by kcott
in thread Placement of custom modules outside of home directory?
by mldvx4
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |