If you are sufferring from conflicts, just install another perl for each project.

As long as the perls don't know about each other, you have a lot of safety.

From then on make sure people who do stuff to the perl installation directory just make a note of it, and keep the log under revision control.

Third party modules should go into your source control for each project, should be renamed (even trivially). Renaming is crucial, don't underestimate it. If they need complex installation, you should have your own installation tree for each project.

To sort out dependencies, you could either 'make dist' for each of your modules, and then put them in your own fake CPAN mirror and have CPAN.pm install their dependencies, or you could install the originals as part of the process. Since your modules would have been renamed, they don't interfere.

The recipe script for installing all the dependencies should be under the project's source control. It should know how to fetch perl, build it, get all the modules, install them in the right prefix, and so on and so forth. stvn needed something similar, and that's why Verby was written. It might be useful for making this kind of installation script, but if you are going to script CPAN installations you might aswell use CPANPLUS's backend modules - they are more flexible to program.

-nuffin
zz zZ Z Z #!perl

In reply to Re: How do you manage module deployment? by nothingmuch
in thread How do you manage module deployment? by fce2

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.