XP is just a number | |
PerlMonks |
Re^6: Do Pure Perl CPAN packages really need to use ExtUtils::Command::MM?by ELISHEVA (Prior) |
on Feb 18, 2011 at 07:38 UTC ( [id://888860]=note: print w/replies, xml ) | Need Help?? |
Technically, all MakeMaker is doing is a pass through too. Each just makes a shell call to its own implementation of test, install, etc. Since we are talking pure Perl modules here (check thread title) those are the only targets that are relevant. Whether pssthrough is a suitable way to deal with C/C++ builds is another discussion entirely. If anything Module::Build's shell commands are safer. MakeMaker's target implementation requires quoted parameters and long lists of files passes on the command line. Both are known to cause portability problems because of differences in shell quoting rules and limits on command line length. Module::Build's perl calls have none of those issues because there are no quoted parameters or file lists - instead it relies on its stored project metadata. Given that both MM and MB command lines are only making Perl calls to their own libraries, "passthrough is crap" is little more than a bald statement that you believe Module::Build is crap. I didn't post this question to take sides in the "I hate Module::Build" debate. I posted this question because I wanted to understand what the cost benefits were. How big of a community refuses at any price to use Module::Build or anything tainted by it (e.g. a Makefile whose targets are implemented by Module::Build)? How big of a community can't download Module::Build but can download CPAN modules (jetthro argues such a community is likely to be very small indeed). What are the costs of supporting their needs? (how much time in this case, no one is getting paid here). Does it occur to you that my time is valuable and you are asking me to spend it to support your hatred of Module::Build? If so, I need a good reason. "It's crap" is way too vague to count as a reason. I personally would have preferred you had posted a thoughful and well written essay on _why_ you trust MakeMaker so much more than Module::Build. Even if you said nothing more than "its the new kid on the block and I just don't trust it" that would have mattered more to me. Your feelings as a member of the "I hate Module::Build" club do count. Looking at the tenor of the responses on this thread and who has participated and who has not, I'm inclined to believe that the answer to my question is something like this: aside from some very vocal (if anonymous) individuals like yourself, most people simply don't care. They just want the install to work. Period. Whatever I do that makes that happen will make them happy. If that's the case, I would have to say that one is more likely to get a reliable install using a Module::Build backed makefile than not. Do you have concrete counter arguments and examples?
In Section
Seekers of Perl Wisdom
|
|