Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

comment on

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

That is what I do because my company doesn't keep Perl modules in a place that Perl knows anything about.

If you provide the PREFIX variable to the perl Makefile.PL command you can install a module anywhere you want using the standard process. e.g

perl Makefile.PL PREFIX=/my/custom/INC/dir/ make make test make install

This hasn't always worked exactly as planned but it has worked for me for many years. I never install modules into the OS perl distribution and always install modules in my home directory when I'm on a system where I can't install another perl distribution or don't have root priveleges.

Refer to the perlmodinstall man/perldoc page

CPAN and CPANPLUS can be configured to use this PREFIX by default so that you can install modules in your special place as easily as into the distribution. Just refer to their documentation.


In reply to Re^2: What Makefiles do by clscott
in thread What Makefiles do by throop

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.