# from Hans Dieter Pearcey
# on Wednesday 08 April 2009 12:35:
>On Wed, Apr 08, 2009 at 12:26:17PM -0700, Eric Wilhelm wrote:
>> You're saying there is a debate about whether stagnation is a good
>> idea?
>
>I'm missing the connection between "stagnation" and "Module::Install",
> here. Or were you talking only about EUMM?
The PBP review says "maybe" on M::B, but nothing about M::I. If you're
going to recommend that new users use M::I instead of EU::MM or M::B,
you really need to hang an even bigger maybe on that one.
EU::MM will "just work" because it never (except re INSTALLDIRS) changes
and predates all of the client tools. The drawback for authors is that
it never changes and that functionality is limited. The drawbacks for
users are some subtle interface nits related to the fact that it uses
make (and shells out to perl for every file manipulation.) There's a
less visible "lack of new features" - because it never changes.
M::B will "just work" as soon as all of the client tools are updated.
The drawback for authors is getting bug reports from users who don't
have updated client tools. The drawback for users is also in the
client tools.
M::I will "just work" until something goes wrong with the bundled
version, at which point the author using it *must* release a new
version to fix it. It is also susceptible to EU::MM *ever* changing.
Now that we have configure_requires, EU::MM might start changing, which
would completely break M::I.
> and it doesn't matter
> (to that subject) that you say very forcefully that there is no
> reason not to use Module::Build, and call people who do not want to
> use it "irrational", because that all is *part* of the "controversy",
The pain of making it possible to have more than one build tool, or to
have our build tools ever change (without bundling the world into each
dist) has a long history. I can understand that from the standpoint of
people not having time to mess with it, but how much of the pain is
just a result of the momentum of the pain?
--Eric
--
Speak softly and carry a big carrot.
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
