Skip Menu |
 

This queue is for tickets about the Module-Build CPAN distribution.

Report information
The Basics
Id: 5280
Status: resolved
Priority: 0/
Queue: Module-Build

People
Owner: Nobody in particular
Requestors: andrew [...] pimlott.net
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 0.21_01
Fixed in: (no value)



Subject: please add MakeMaker user-level compatibility
Download (untitled) / with headers
text/plain 586b
It's exceedingly frustrating that Module::Build breaks the conventions of MakeMaker installations. I was first surprised that the PREFIX parameter is not supported, then even more surprised that there is no simple way to get the same effect. Since I have a collection of modules in my personal MakeMaker-style tree, it looks like I will have to create a second tree for Module::Build modules and put them both in my PERL5LIB. When I install a module, I will have to figure out which build system it uses and remember which parameters to use. Is there any hope for a simpler outcome?
Download (untitled) / with headers
text/plain 799b
It should be possible to specify whatever arbitrary installation location you want, using the 'install_path' parameter: http://search.cpan.org/~kwilliams/Module-Build- 0.24/lib/Module/Build.pm#install_path The only reason I've taken a fairly hard-line stance on not supporting the 'PREFIX' functionality of MakeMaker is that it defines some fairly wonky DWIM semantics, and the user can easily end up installing to somewhere totally *crazy*, having little or no relationship to what they specified in the PREFIX parameter. Module::Build's 'install_base' parameter is similar, but without the pitfalls associated with PREFIX. Your point about compatibility is well-taken though, and please feel free to contribute any suggestions you might have on the Module::Build mailing list. -Ken


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.