Bug #71901 for Module-ScanDeps: scandeps -R finds too much

Mon Oct 24 13:06:59 2011 SREZIC [...] cpan.org - Ticket created

Subject:

scandeps -R finds too much

With the following module, saved as Foo.pm: package Foo; use Template; 1; and the command: /usr/perl5.12.3/bin/scandeps.pl -R Foo.pm I get a large list of dependencies: 'Template' => '2.22', 'Template::Alloy' => '1.016', 'Template::Alloy::Compile' => 'undef', (snipped 120 lines) 'Template::VMethods' => '2.16', 'Template::View' => '2.91', I would expect just 'Template', as the only dependency. Note that Template::Alloy is not even part of Template-Toolkit. Regards, Slaven

Mon Oct 24 18:00:01 2011 RSCHUPP [...] cpan.org - Correspondence added

On 2011-10-24 13:06:59, SREZIC wrote: Show quoted text

> ... > I get a large list of dependencies: > > 'Template' => '2.22', > 'Template::Alloy' => '1.016', > 'Template::Alloy::Compile' => 'undef', > (snipped 120 lines) > 'Template::VMethods' => '2.16', > 'Template::View' => '2.91',

That's on purpose. Template.pm loads lots of Template/*.pm and Template/Plugin/*.pm modules at runtime that can't be detected by static analysis. So Module::ScanDeps punts and depends on every installed module "below" Template - just to err on the safe side [1]. Template::Alloy is just collateral damage (and really should not have used this name in the Template:: namespace in the first place, but that's the anarchy of CPAN). Cheers, Roderich [1] The primary customers of Module::ScanDeps are PAR and PAR::Packer where the main concern is that we pack in anything that could potentially be loaded by the given script.

Mon Oct 24 18:00:03 2011 The RT System itself - Status changed from 'new' to 'open'

Mon Oct 24 18:00:04 2011 RSCHUPP [...] cpan.org - Status changed from 'open' to 'rejected'