cyclone has asked for the wisdom of the Perl Monks concerning the following question:
I was attempting to synchronize my development/test environment with the actual production environment and the autobundle option in the CPAN.pm module wasn't working the way I thought it would.
Here is the setup:
We have a development network (1 server, 4 workstations) that has had many Perl modules installed to facilitate our system. I was using the CPAN.pm module to do all admining of said modules. Well... I was under the impression I could take the snapshot file created bycpan> autobundleand place it into the production network ( 40 workstations ) and runperl -MCPAN 'install Bundle::Snapshot_2000_05_30_00'But it doesn't work completely. I had to install a few by hand. So I pose the question:
Does anyone have some wisdom to share regarding keeping the modlist sync'd between dev and production environments?
TIA
Here is the setup:
We have a development network (1 server, 4 workstations) that has had many Perl modules installed to facilitate our system. I was using the CPAN.pm module to do all admining of said modules. Well... I was under the impression I could take the snapshot file created bycpan> autobundleand place it into the production network ( 40 workstations ) and runperl -MCPAN 'install Bundle::Snapshot_2000_05_30_00'But it doesn't work completely. I had to install a few by hand. So I pose the question:
Does anyone have some wisdom to share regarding keeping the modlist sync'd between dev and production environments?
TIA
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: CPAN.pm/autobundle usage
by perlcgi (Hermit) on Jun 02, 2000 at 16:38 UTC | |
by cyclone (Novice) on Jun 03, 2000 at 04:36 UTC | |
by perlcgi (Hermit) on Jun 04, 2000 at 00:25 UTC | |
by cyclone (Novice) on Jun 04, 2000 at 08:50 UTC |
Back to
Seekers of Perl Wisdom