I personally don't like Module::Build's complete disregarding of well-established items like PREFIX and such. Especially when it recognises that it's been passed those items. It's incredibly arrogant, IMO.
(update: fix a minor grammar issue) | [reply] |
Um, not implementing something is not arrogant. Have you ever looked at the code in EU::MM that makes PREFIX do its thing? Would you care to re-implement that?
| [reply] |
I personally don't like Module::Build's complete disregarding of well-established items like PREFIX and such. Especially when it recognises that it's been passed those items. It's incredibly arrogant
No it's not.
The whole point of Module::Build is to re-think how module installation works. The EU:MM PREFIX logic is very complicated. The M::B install_base logic is far simpler and works in more places.
If you want M::B to do exactly the same as EU:MM why bother?
| [reply] |
If you want M::B to do exactly the same as EU:MM why bother?
I don't bother. Other module authors do, though. As for why it matters: I'm a stickler for backward compatibility and tradition. That and I'm afraid of the Perl module build process being mutated into something like the GNU autotools suite. If you've ever tried to run an autogen.sh on a BSD system, you know what I mean. If you don't, search the FreeBSD mailing list archives.
Think about it this way: I'm so pleased with the user interface of the current system that any sort of change bothers me. :)
| [reply] |
| [reply] |
