comment on

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

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.


No such thing as a small change
	PerlMonks