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... ;-)
Bundling is a total non-issue.
You create an /inc directory in your distribution, and then you make
sure you have a no_index entry in your META.yaml.
Done.
The process has been automated in Module::Install for you (not that I'm
suggesting you move) and probably should be automated in Module::Build
as well. Anything in /inc or /t (and possibly /examples /demo etc)
shouldn't ever be indexed so it's fairly straight forward to auto-add a
no_index entry if these exist.
Bother the indexer and search.cpan obey these properly.
This is almost certainly what Module::Build should be doing. Bundle the
pure-perl version of version in /inc/version.pm and have /inc somewhere
down the back of @INC as a fallback.
Adam
