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

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 seems to me that testing by smokers is also in the order Lunix, Mac, MSWin. That is pretty strange to me, if we want perl to be nice to novices, and we want perl to grow and thus live.

    Maybe it should be a goal for Strawberry Perl to be able to be shipped with cpan testing on, so anyone who can type "cpanp" at the MS command window (not many, I wager) will be a tester of everything they think they need. If they want to turn it off, the directions will be right there.

    The major problem I see is only an email return address, but if a spam filter can not tell a test report from a UCE, all is lost. Well, maybe that and a way to use http as a transport method. And a way to pick up the http proxy out of the windows settings. And... and... and...

    Still, a worthy goal, with room alnog the way for useful progress, if only to allow novices to become testers.

    • It is a goal to enable reporting FAIL by default, but unfortunately CPAN::Reporter isn't good enough yet. It needs to support HTTP, and it needs to be vendor-configurable so it can just work out the box without the need for a file in the user's home directory.

      • Agreed. I note that HTTP transport of reporting has been talked about a long time. I think the closest they got, was they allowed it, if you were running your own http server, and then you could mail it out from there. So that seems to have fallen off the list.

        To me that is "GOTO 10". When asked if THEY would put up a public server, the answer was, "no". Oh well, I know this will be construed as complaining without correcting, but hey, I want perl to succeed, and I am not of the class to submit patches

        • Once we got support for vendor-configurable CPAN::Reporter, I plan to build a "standard" HTTP reporting channel for strawberry. But until CPAN::Reporter can be set up that way, it's pointless.

          • Glad to hear you are on it! Thanks.

            Bit what does it mean to have a vendor-configurable CPAN::Reporter? Who would need to do that, or contribute?

        • I think the closest they got, was they allowed it, if you were running your own http server, and then you could mail it out from there.

          That was as close as it was possible to get by adding HTTP support to just the client. That’s the easy part. The server side needs actual infrastructure, which needs to be developed (it’s more complex than the client), then set up on machines facing the open internet, then kept running under the load of report submissions.

          When asked if THEY would put up a public