Eric Wilhelm wrote:
Was there a discussion at one point about M::B bundling and/or bootstrapping its non-core dependencies?
This discussion is complicated by the fact that both M::B and version will be core in 5.10.0, so we only need to deal with fresh installs.
IMO, asking your dependencies to use EU::MM is at least sub-optimal. This should not be version.pm's problem.
But that was the best way to handle it quickly.
AFAIK, EU::MM never depended on anything that hadn't always been core.
Well, version can depend on EU::MM, because EU::MM is core, so I'm not introducing any additional dependency.
Which would hurt less? 1. bundling dependencies - "cpan version" would cause two installs of version.pm (big deal?)
This last point is actually a big deal. If we had gone the bundled route, we'd have to make sure that cpan only indexed the standalone version.pm release, since otherwise it could happen that trying to install only version.pm would also install Module::Build.
Anyways, moot points all around... Nothing to see here... Move along, move along... ;-)
John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748
