----- Original Message ----
From: Bill Moseley <[EMAIL PROTECTED]>
> On Mon, Jun 18, 2007 at 11:26:45AM +0100, Paul LeoNerd Evans wrote:
> > My main objection to Module::Install is that it lives in the distribution
> > itself, rather than being out-of-tree, living on the target system.
<snip>
> > Moreover, they contain a snapshot of
> > whatever version of M::I was current at the time it was built, or, maybe,
> > whatever version the module's developer had at the time.
>
> Yes and no. At least you know the version included worked -- where an
> earlier or later version might not.
You only know that this version worked on the module author's machine with the
module author's build and environment. And even then you don't know that
because they might have left out a 'requires' for a module they have installed.
> 2) A way to say some modules are recommended but not required.
> Do any installers support that?
Sure. From the Module::Build Build.PL file :)
recommends => {
'Archive::Tar' => '1.08',
'ExtUtils::CBuilder' => 0.15,
'ExtUtils::Install' => 0.30,
'ExtUtils::ParseXS' => 1.02,
'Pod::Readme' => 0.04,
'Module::Signature' => 0.21,
'version' => 0.661,
},The Module::Build::Authoring docs specifically states that
this key is for "versions of modules that are recommended to provide enhanced
functionality".
Cheers,
Ovid
