Skip Menu |

This queue is for tickets about the Module-CPANTS-Analyse CPAN distribution.

Report information
The Basics
Id: 111577
Status: open
Priority: 0/
Queue: Module-CPANTS-Analyse

People
Owner: Nobody in particular
Requestors: domm [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: (no value)
Fixed in: (no value)



Subject: New version 0.340 of Module::ExtractUse might report more uses
Hi! I've just released a new version of Module::ExtractUse including work done as part of the CPAN Pull Request Challenge to report usage of modules via Module::Runtime and Class::Load. This might have some consequence on CPANTS / reported deps etc. Just a short heads-up, even though I don't think the changes will cause any real problems (they may uncover some missing dependecies, though..) Greetings, domm
On 2016-01-30 12:17:09, DOMM wrote: Show quoted text
> Hi! > > I've just released a new version of Module::ExtractUse including work > done as part of the CPAN Pull Request Challenge to report usage of > modules via Module::Runtime and Class::Load. > > This might have some consequence on CPANTS / reported deps etc. > > Just a short heads-up, even though I don't think the changes will > cause any real problems (they may uncover some missing dependecies, > though..)
They may cause new kwalitee failures if the kwalitee metric interprets uses of Module::Runtime and Class::Load as "should be in required deps", which isn't always correct -- generally these modules are being employed when deps are needed *conditionally*, meaning they might be more appropriate as 'recommends' or 'suggests' dependencies instead.
On Sun Jan 31 13:29:16 2016, ETHER wrote: Show quoted text
> On 2016-01-30 12:17:09, DOMM wrote:
> > Hi! > > > > I've just released a new version of Module::ExtractUse including work > > done as part of the CPAN Pull Request Challenge to report usage of > > modules via Module::Runtime and Class::Load. > > > > This might have some consequence on CPANTS / reported deps etc. > > > > Just a short heads-up, even though I don't think the changes will > > cause any real problems (they may uncover some missing dependecies, > > though..)
> > They may cause new kwalitee failures if the kwalitee metric interprets uses > of Module::Runtime and Class::Load as "should be in required deps", which > isn't always correct -- generally these modules are being employed when > deps are needed *conditionally*, meaning they might be more appropriate as > 'recommends' or 'suggests' dependencies instead.
Unfortunately, there seem several issues in the newer versions of Module::ExtractUse (failing to list Module::Runtime itself, etc). I'll post issues/send pull requests when I finish sorting them out.