Skip Menu |
 

This queue is for tickets about the Dist-Surveyor CPAN distribution.

Report information
The Basics
Id: 95712
Status: open
Priority: 0/
Queue: Dist-Surveyor

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

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



Subject: Add a blacklist of distros to ignore in responses from metacpan
Download (untitled) / with headers
text/plain 758b
Sometimes people accidentally upload distributions that contain many modules from cpan that shouldn't be part of the distro. Two examples are: HTTP-CookieMonster-0.06 DateTime-ISO8601-Interval-0.001 These cause lots of false matches in dist-surveyor. Often it works out the right answer anyway, but not always. So these broken distros can cause more problems beyond spurious warnings like: Test::FailWarnings seen in DateTime-ISO8601-Interval-0.001 - now overridden by Test-FailWarnings-0.004 TAP::Formatter::Color seen in HTTP-CookieMonster-0.06 - now overridden by Test-Harness-3.30 It would be nice to find an automated way to avoid this but meanwhile a command like option that would let the user blacklist problematic distros would be very helpful.
Download (untitled) / with headers
text/plain 491b
Show quoted text
> Sometimes people accidentally upload distributions that contain many > modules from cpan that shouldn't be part of the distro.
Even though you might consider these distros "broken", a user might still have them installed. So completely blacklisting the distro doesn't seem like the right solution. In my experience, this happens most often with authors that use perlbrew and local::lib. So usually, you can just ignore any package in the distro that lives under the local/lib directory.
Download (untitled) / with headers
text/plain 617b
On 2014-12-30 15:48:14, THALJEF wrote: Show quoted text
> > Sometimes people accidentally upload distributions that contain many > > modules from cpan that shouldn't be part of the distro.
> > Even though you might consider these distros "broken", a user might > still have them installed. So completely blacklisting the distro > doesn't seem like the right solution. > > In my experience, this happens most often with authors that use > perlbrew and local::lib. So usually, you can just ignore any package > in the distro that lives under the local/lib directory.
Maybe it's enough to just ignore modules marked as "UNAUTHORIZED"?


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.