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

Replies are listed 'Best First'.
Re: CPAN.pm/autobundle usage
by perlcgi (Hermit) on Jun 02, 2000 at 16:38 UTC
    Hope this reply isn't naive, let me know if it is...
    If the machines are all the same architecture check out tree-sync.pl in the CPAN administrative scripts section at http://www.perl.com/CPAN-local/scripts/CPAN/Administrative/index.html. It compares two directories recursively, prints out a report and generates a batch file that can sync two trees. Then maybe you could do something along the lines of this
     perl treesync.pl /usr/local/lib/perl5/site_perl /mnt/prodn/usr/local/
+lib/perl5/site_perl

    [download]
    Maybe then, grok the command file for a reality check, then run it.
[reply]
[d/l]
      I read the documentation on treesync.pl and a co-worker posed this question:
      How is it better than rdist? Are there benefits to using the Perl code over the built-in sync utility?
      BTW... we use *NIX here.
      Thanks
[reply]
        How is it better than rdist?
        Good question? It is written in Perl :-) but rdist users rlogin, and dupes the permissions which might be an easier to maintain solution. I note some other discussions here by fellow perlmonk corion mention rsync which could well be the way to go. This document summarizes the pro's and con's of rdisk v rsync. rsync seems to win hands down.
[reply]

Back to Seekers of Perl Wisdom