After a file has gone through 'make' is there a way to specify a new install path when performing 'make install'? Or does anyone have a good way of distributing modules to various boxes?
If you can't NFS (or AFS) mount from a centralized server
then you could possibly negotiate a standard where
you do two things:
- Establish a standard where you have a place where all
third party software goes. In my shop we use the
standard point of /usr/local/software and further
every version of the software we are "keeping"
gets installed in a subdirectory named after its version
for instance /usr/local/software/perl-5.8.0
-
With that in mind you then put in symoblic links as
needed to that standard places. Such as /usr/bin/perl
would be a symbolic link to /usr/local/sofware/perl-5.8.0/bin/perl.
The beauty of having the subdirectories with mutltiple
versions is that if you have a developer who's Perl script
needs a different version than what you have in
"production" they can just change the shebang
line as needed. In a previous shop we actually had cases
where scripts used in production would only run under
older versions of Perl and blew up under the latest
and greatest.
From what you have described doing what I propose won't
be easy, but often good things aren't easy to do.
Once you have established this standard then building new
modules and installing them will go much smoother.
Peter L. Berghold -- Unix Professional
Peter at Berghold dot Net |
| Chat Stuff: | AIM: redcowdawg
Yahoo: blue_cowdawg |
| Cowdawg Philosophy: | Sieze the Cow! Bite the Day! |
| Clever Quip: | Nobody expects the Perl Inquisition! |
| Non-Perl Passion: |
Dog trainer, dog agility exhibitor, brewer of
fine Belgian style ales. Happiness is a warm, tired, contented dog curled up at your side and
a good Belgian ale in your chalice. |