in reply to Re: Removing Modules
in thread Removing Modules

Why do I want to do it? I have three systems running here:
  1. a production (external) web server, with Apache, mod_perl, EmbPerl and similar stuff.
  2. A production (internal) system, with a number of Perl applications and our intranet server
  3. My development box
The development box now has a number of modules on it that I put on, kicked around with, and decided not to make use of. However, we try to keep all three systems in sync as far as versions, software installed and so on. I want to make sure that the development server can have stuff removed that I don't wish to run in production.

Replies are listed 'Best First'.
Re: Re: Re: Removing Modules
by Fastolfe (Vicar) on Feb 02, 2001 at 08:24 UTC
    It might be easier/safer to start from a minimal installation with the stuff you want, and then pack up and distribute that filesystem to your other machines, nuking the older copies. So long as the architectures and Perl versions are the same across systems, the /usr/lib/perl5 hierarchy should be reasonably portable. That would also greatly assist your "in sync" needs.
[reply]
      You'll need the corresponding Perl binaries, if there's any chance anything was built differently between machines. Here's my script for building a tar-gzip file that I use to update the sites I keep in sync: 
      cd /usr/local/
find lib/perl5 -name "*.a" -o -name "*.html" > /tmp/nocopy
gtar zcvf /tmp/Perl5.tar.gz lib/perl5 -X /tmp/nocopy bin/perl* bin/pod
+* lib/libperl*
rm -f /tmp/nocopy

      [download]
      This avoids copying the library and HTML doc files that aren't needed at the other sites.
[reply]
[d/l]

In Section Seekers of Perl Wisdom