Hmm.. perhaps I wasn't clear. I don't want to overwrite the existing perl on the build system, but I do on the deployment targets, which is the same perl in the same location (because it's using the packaged perl 5.6.1). I have no need to keep 5.6 on the deployed machines.
If I build perl to live in, say, /apps/perl-5.8.6, it also wants to install its libraries there, no? At least, that's what I can figure from Configure..and that will break the package, because the paths will not reflect those in deployment.
I used the Config.pm from the 5.6 installation to configure 5.8.6, but it's confusing to say the least - particularly this is unclear:
In some special cases, particularly when building $package for distrib
+ution, it is convenient to distinguish the directory in which files s
+hould be installed from the directory ($prefix) in which they will ev
+entually reside.
I'll try your chroot idea, although it looks like that means I'll have to configure & build perl twice..
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.