Matisse Enzer wrote:
#2 has it's benefits too - you could even mirror all of CPAN, and
just maintain a script with "install" commands to install the
versions you
want;
install "KWILLIAMS/Module-Build-0.27_04.tar.gz";
etc. That makes both upgrading easy and makes your build process
independant from the availablity of your favourite CPAN mirror.
Yes, it also means the build process can take of resolving
dependencies. The downside is having yet-another-repository.
The upside is that it might be using less bandwidth in the long run.
That may or may not be relevant, but I have gotten the impression that
large companies care more about it that small ones because they've
outsourced everything to some draconian IT + internet service provider. ;)
You might want to look at
http://search.cpan.org/~rjbs/CPAN-Mini-0.40/lib/CPAN/Mini.pm and
possibly
http://search.cpan.org/~ssoriche/CPAN-Mini-Inject-0.18/lib/CPAN/Mini/Inject.pm
which enables you to insert your custom modules to the CPAN mirror.
Then, you can install both CPAN modules and custom code from the same
source provided you can package your code as a module. (It should
certainly be possible for most things including scripts.)
When deploying to a remote site, you can strip down the mini CPAN to
just your distributions and their dependencies and burn that on a CD or
similar.
Steffen
