On Sat, Sep 12, 2009 at 12:57 AM, Ron Savage <r...@savage.net.au> wrote: > My concern is authors choosing to include a dev version of module, which > is in conflict with my policy of - as far as humanly possible - of never > installing a dev version. Simple! > > Now what happens when they do that, and the install succeeds, but when I > use their module with my non-dev - and presumably older - version, their > module does not work. E.g. is has an incompatible API. > > Or is this impossible, because I misunderstood what's going on?
You've misunderstood. The bundled modules are *only* the 'configure_requires' modules. Generally, that means Module::Build and anything custom necessary to get Build.PL to run. Bundled modules are not installed. In some cases, I could see a dev version of M::B being bundled. E.g. someone really desperately wants File::ShareDir support, but we haven't released 0.36 yet. They could bundle 0.35_XX and have ShareDir support for installation. I think restricting that (a) is hard and (b) defeats a potentially important use case. David
