in reply to About modules version on ActiveState's PPM

I hope this can help a little to clarify if something should be done by the module author or if something should be said to AS.

I'd suggest something along the lines of "Reporting test and installation errors to module authors might help them release new versions which would install flawlessly."

I've never received any feedback from the ActiveState build farm, though I'd reject some of the errors reported on some of my modules (explicitly marked dependency not installed, for example, or CPAN module not configured) as Not My Problem.

  • Comment on Re: About modules version on ActiveState's PPM

Replies are listed 'Best First'.
Re^2: About modules version on ActiveState's PPM
by runrig (Abbot) on Jan 07, 2005 at 22:05 UTC
    I've never received any feedback from the ActiveState build farm, though I'd reject some of the errors reported on some of my modules (explicitly marked dependency not installed, for example...
    They've considered sending out failure notices, and have so far rejected it because the current automated system is loaded with kinks, and they don't want to spam authors with false failure notices (like the one above, where it's not your fault, but a prerequisite module that failed). One of my modules depends on MIME-tools, and since it fails the build, my module fails also. Since there was a version of MIME-tools that did build, I emailed the ppm mailing list and my module is available in their repository. I also like to periodically check the build status of various modules (I like that link better than the full list of modules, which takes too long to load).