rak has asked for the wisdom of the Perl Monks concerning the following question:
Hello,
I'm putting together an install script for our Linux machines, and I want the user to need to interact with the install as little as possible.
One part of this install is a bundle of Perl modules. Previously, we have done this by defining a bundle and doing a force install of the bundle in CPAN. However sometimes it takes 2 attempts to get all the dependencies resolved, and some modules require user input as part of the CPAN install.
Are there any disadvantages to replacing /usr/lib/perl5 with a zipped install of the modules instead of using CPAN in this instance? (The Redhat and Perl versions will be the same across machines, and ideally the Perl modules should all be the same versions, which this method provides ensures).
Thanks in advance for your advice!
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Best way to package perl modules for deployment
by zby (Vicar) on Apr 28, 2003 at 15:39 UTC | |
|
Re: Best way to package perl modules for deployment
by perrin (Chancellor) on Apr 28, 2003 at 15:46 UTC | |
by rak (Novice) on Apr 29, 2003 at 08:47 UTC | |
|
Re: Best way to package perl modules for deployment
by nite_man (Deacon) on Apr 29, 2003 at 07:12 UTC | |
by bwana147 (Pilgrim) on Apr 29, 2003 at 10:38 UTC |