Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

Welcome Gib,

I have never built a RPM on *nix, but I have multiple Perls on all of my *nix boxes. I compile the source in my home directory, and specify to install it into '/usr/opt/perl.5.xx.xx', and then I come up with names that I use to generate symbolic links, i.e.

ln -s /usr/opt/perl5.14.2/bin/perl /usr/local/bin/perl.14.2 ln -s /usr/opt/perl5.14.2/bin/perl /usr/local/bin/myperl ln -s /usr/opt/perl5.14.2/bin/perl /usr/local/bin/vmperl . . .

When I build a new Linux server, I just 'tar -c' the '/usr/opt/' directory and the linked Perl*, and then ftp the tar file to the new system. (Note: I do not touch the standard Perl shipped with the Linux distribution.) Then using 'tar -x' I install all my Perl versions on the new Linux server. One advantage is that all CPAN requirements will be on the new server. I have done this between Linux distributions successfully, but I may just have been lucky.

If you need specifics, ask away! It just might help another admin in the future. If you need to get the RPM, another monk will have to help.

Regards...Ed

"Well done is better than well said." - Benjamin Franklin


In reply to Re: Create an RPM for custom compiled Perl ? by flexvault
in thread Create an RPM for custom compiled Perl ? by Gib

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.