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 ]

barbie (2653)

barbie
  reversethis-{ku. ... m} {ta} {eibrab}
http://barbie.missbarbell.co.uk/

Leader of Birmingham.pm [pm.org] and a CPAN author [cpan.org]. Co-organised YAPC::Europe in 2006 and the 2009 QA Hackathon, responsible for the YAPC Conference Surveys [yapc-surveys.org] and the QA Hackathon [qa-hackathon.org] websites. Also the current caretaker for the CPAN Testers websites and data stores.

If you really want to find out more, buy me a Guinness ;)

Links:
Memoirs of a Roadie [missbarbell.co.uk]
[pm.org]
CPAN Testers Reports [cpantesters.org]
YAPC Conference Surveys [yapc-surveys.org]
QA Hackathon [qa-hackathon.org]

Journal of barbie (2653)

Monday April 19, 2004
09:55 AM

ActiveState testing

[ #18391 ]
Spotted this link by accident over the weekend:

It contains all the test results when ActiveState have attempted to create PPMs for their repository. Discovered a few of mine need some updates. Ooops!


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

ActiveState testing 8 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • For reporting the fscking bugs when you find them. Not. I never even knew that their custom version of the CPAN testers existed.
    • Me neither. It would be nice, with the number of different setups they have, for them to use Test::Reporter somehow. If I can get it to work on Win32, I'm sure they'd find it a doddle.
    • ...For reporting the fscking bugs when you find them.

      What I heard was that it was on the todo list, but the process is far from perfect, so they're not ready to turn that particular feature loose yet.

      • I hope the change their minds. I shall be checking those pages a little more for my modules at least. It might improve the ActiveState PPM repository if they did send reports out, as there have been a few modules I was surprised to find unavailable. Now I know why.
  • Seems to be some pretty weird stuff going on there.

    For example, this problem [activestate.com] (warning - very large page) seems to be caused by their program not being able to configure CPAN.pm correctly. And this one [activestate.com] seems to imply that they aren't automatically installing pre-requisites.
    • Module::Build is a law unto itself anyway. It can't be installed without manual installation. I have yet to have a successful cpan smoke test of Module::Build.

      CPANPLUS has been having difficulties installing prerequisites [cpan.org] for the past few months, so I wouldn't blame ActiveState too much for having odd reports either.

    • Makefile.PL has no business running CPAN.pm automatically, especially not when STDIN is not a tty. You would be surprised to see how many broken Makefile.PL scripts assume they are being run interactively. I wish module authors would instead provide complete PREREQ_PM listings.
      • While in most cases I'd agree, there are some modules where an interactive session does aid installation. However, most of those that do interactive sessions properly, account for default values so a return will do the right thing.

        It's the installations that cycle round in endless circles, when the right value hasn't been entered that gets me. There is a HTTP module that sits in a while loop until it gets the right entry. If you don't get the right entry after the second time (the first blank may be accid

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.