You don't say so, but if the machines exist on the same network, I would be inclined (after testing of course) to share out the perl library directories from a central server. This allows you to maintain one directory tree, instead of having to physically/logically touch each machine.

Also, you don't mention whether or not you use the same perl version across all of the systems. If not, you will wind up testing each and every combination.

If neither is an option, I would set up a multi-boot system with all (4?) systems available. Then, set up a master directory structure that includes the sub directories for each architecture and perl version.

Super Search will give you pointers to how to set up a "private" perl library structure. Once that structure is set up, you will be able to simply install the appropriate modules using a combination of CPAN (or CPANPLUS) and the individual environments. Simply build (and test) for one environment (say, 5.4 x86_64) then create an autobundle module. Now, use that to create the other environments, then install the entire environment on a shared drive (if possible) or rsync the entire directory structure on each machine.

In reply to Re: managing cpan across machines by proceng
in thread managing cpan across machines by bushidoka

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.