As with several other iterations of this debate, though, this consists
of you pointing out some flaws, and someone else trying to calm you down
or ameliorate the debate. I do appreciate your thoughts and analysis of
the situation, but patches (or even proposed solutions) speak a lot
louder than speaking loudly.
Most often from my perspective it consists of being told the problem
either a) isn't a problem, or b) doesn't impact many people at the
moment, or c) We'll look into it.
Because I'm not a M:B user, and not really part of the "community" I
haven't felt it's really my place to make large changes to the design of
M:B.
Further, most of these changes require co-ordination between multiple
modules, which makes changes harder again.
If you are requesting design proposals, I am happy to suggest some.
As a starting point, I think that the idea of CPANPLUS instantiating
Module::Build objects directly has to go, and favour of a CPAN.pm style
loosely coupled execution approach, as others have mentioned.
It introduces the flexibility to deal with subsequent solutions for
other parts of the problem.
Since YAPC::NA is the only conference I'll be at this season, and
Audrey will be present as well, it would seem that a meeting or
BOF'like session at YAPC::NA would be ideal for setting out the
specifics of the problem and looking at the most appropriate solutions.
Unfortunately neither Randy nor I will be there, nor will I be at TPC
either (and I think neither will Randy). If there's a time that works
for other people at YAPC though, I bet I could teleconference or iChat
myself in, or something like that, if that would be helpful and not too
much hassle.
That might be workable.
Adam K
