There were times when a pathetic addition to the CPAN was merely a minor annoyance, easy to tolerate as such a module did not interfer with one's own work.
Nowadays however, one rotten CPAN egg is capable of making tests of your own modules fail, as can be seen here and here.
Mind you, the offending module isn't used nor mentioned anywhere in the modules whose tests it can make fail. The failures happen because this pathetic piece of shit doesn't adhere to any CPAN packaging standards and its files and directories somehow get merged with those of other modules on tarball-extraction.
And now I am waiting for those who still claim that CPAN's policy should be as liberal as possible when it comes to uploads. No, it shouldn't. Instead, too obvious breaches against CPAN conventions should be denied their upload. Furthermore, those that were uploaded in the past ought to be deleted immediately.
I suppose it's not going to happen. That means that my modules will continue to fail their tests on that particular machine until its admin finally removes the offending files by hand.
at least.. (Score:1)
What specifically? (Score:2)
And how does this module make your own tests fail? What is the harmful behavior it's causing?
--
xoa
Re:What specifically? (Score:2)
With respect to an uploading policy, you mean? I'd say the criterium of extracting nicely into a directory of its own is the very least that should be checked for.
And how does this module make your own tests fail? What is the harmful behavior it's causing?
The harmful behaviour is caused by this module's tarball extracing into the directory
blib/. I suppose that on this machine where the POD-tests fail for two of my modules it was unpacked while being in thePotential for self defense meantime (Score:1)
Bill
# I had a sig when sigs were cool
use Sig;