IMO, I'd do something like...
- have a perl server for each 'flavour' of supported OS - exporting the perl directory.
- for any host, hard mount the perl directory from the appropriate server i.e. the perl server having the matching OS.
Then it becomes merely a task of running
make test install on each of the
perl servers - a task easily accomplished with a suitable make(1) script on one of the servers that runs make using rsh(1) on each
perl server.
Moreover, the above would be simplified (almost immeasurably) if you have a central includeable (if there isn't such a word, there ought to be:-) make(1) script defining the expected/required build state in terms of modules.
In that way, you will...
- Only have to build one platform specific version of the libraries
- Get a scaleable solution.
- Have to re-run the build iff either a module changes (version) or a new module is introduced.
HTH ,
At last, a user level that overstates my experience :-))
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.