If we didn't already have other M::B subclasses in the M::B:: namespace,
then I'd definitely go with Module::BuildX::DistVersion.
If I thought that Module::BuildX:: was a good long-term solution, then
I'd certainly use it.
But the proper long-term solution is a real plug-in architecture. I've
got some thoughts on that I'm going to write up in a separate thread.
That would use Module::Build::Plugin::* (or maybe Module::BuildX::* if
we want to keep the names shorter).
Since Module::BuildX:: would be just a temporary stopgap, I don't really
see the need for it. We already have half a dozen M::B::subclass
modules. If a few more are introduced before the plug-in system is
ready, it won't make any significant difference.
--
Chris Madsen [EMAIL PROTECTED]
-------------------- http://www.cjmweb.net --------------------
