Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

ethan (3163)

ethan
  tassilo.von.pars ... AMrwth-aachen.de

Being a 25-year old chap living in the western-most town of Germany. Stuying communication and information science and being a huge fan of XS-related things.

Journal of ethan (3163)

Thursday September 29, 2005
12:56 AM

CPAN detergent needed

[ #26931 ]

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.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • .. it got really low kwalitee [perl.org] :-)
  • What specifically do you suggest gets checked for?

    And how does this module make your own tests fail? What is the harmful behavior it's causing?

    --

    --
    xoa

    • What specifically do you suggest gets checked for?

      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 the
      • I sort of understand how the reactions against any call for setting a minimum Kwaalliittee or some other "elitist" minimal bar for sucessfull upload is treated as a Modest Proposal [google.com]. But this is worth further consideration -- the very infrastructure that now makes enforcing such possible is what is making lack of it punish good module authors. The penalty for failing the grade need not be as draconian (or procrustean?) as summary deletion; the offending "module" could be relegated to BackPan, until a replac
        --
        Bill
        # I had a sig when sigs were cool
        use Sig;