I am in an environment where very strict control is the rule. We have dozens of machines of the same OS but only 1 box, our development machine, has a compiler on it.

The reason for this is to force developers to test in one environment and apply changes to production environments. This causes a problem with the upkeep of perl. To make things more difficult, my predecessors did not standardize anything. Each machine is slightly different in the @INC and placement of the perl binary.

What I wanted to do was have the ability to use a centralized server, our development box, to load and make modules. Then once the modules had 'make test' done have the directory they are in NFS mounted to the various servers that they may do a 'make install' of the modules needed.

Great in theory, but I have run into a problem when it comes to @INC on the various boxes. When the modules go through 'make' the Makefile is given the destination for 'make install'. This destination is different among machines of the same perl revision so a 'make install' from the NFS mounted file system fails on the target machine.

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?

In reply to Distributed Perl Modules by gnu@perl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.