I understand vaguely supporting PREFIX has become hairy. What I don't understand is, what are the best practices to deal with the situation.

Is tinita's suggestion of using LIB and PREFIX together a best practice for installing modules locally?

Will this ever fail?

If yes, when will if fail?

If no (ie, it shouldn't ever fail), shouldn't the documentation for installing perl modules locally be patched to mention this?

More concretely: if there's a scenario like the one you mentioned, where LIB is calculated from PREFIX, but the PREFIX value was also specified to Makefile.PL, which value will ultimately wind up being used?

In reply to Re^2: What are the "prefix" and "lib" arguments to makefile.pl used for? by tphyahoo
in thread What are the "prefix" and "lib" arguments to makefile.pl used for? by tphyahoo

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.