On Fri, Nov 19, 2004 at 05:26:14PM -0500, Michael G Schwern wrote:
> http://rt.cpan.org/NoAuth/Bug.html?id=8528
>
> Folks want Module::Build and MakeMaker to install files into the same place.
> This is a perfectly legit concern. The problem comes when you use
> "perl Makefile.PL PREFIX=~". MB has no equivalent and its Makefile.PL
> wrapper does not honor PREFIX. This is because the PREFIX algorithm is mad
> on the best of days, broken on the worst and you really don't want to have
> to support two implementations of it.
>
> One idea is to make MakeMaker's prefixification code callable by MB. This
> would let MB emulate PREFIX without having to duplicate the code. However,
> this will require some work on a part of MM that I prefer to just leave alone.
>
> A simpler, and faster to implement, alternative is to go the other way
> around. Have MakeMaker emulate MB's install_base functionality. Its also
> saner and less prone to bugs than PREFIX.
>
> Most of the time people just want a solution to "How do I install modules
> without being root". install_base does a better job of that than PREFIX.
>
"Me too".
Executables to bin, perl modules to lib/perl or similar.
I don't really care about whether a module is architecture specific
or what have you. I want to be able to set $PATH and $PERL5LIB to something
obvious and have my libs "just work".
I don't really care what the mechanism is as long as it is obvious
and documented. What I don't want is to have to root around under
$PREFIX to try to figure out how to set $PERL5LIB to get all the necessary
libraries included, or to have to set 10 different settings during the
build process to make it go.
Ignorance should be bliss, really. :-)
Austin
