Slash Boxes
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.
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 em

    • 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 to Reporter, but I know a problem for novices when I see it, after making my way through SMTP::TLS so I could smoke.

        The top global tester of CPAN _used_ to test MSWIN and cygwin, and I can only believe they burned out on that, so what are novices supposed to do, to help?

        I try to do some of that now, but I am really just a novice, only 15,000 tests done. When I get some MX problem, there is not much I can do except beg the list.

        But CPAN and testing are one of the gold mines of perl, and CPAN is hardly being tested on MSWIN.

        How about a metric chart of tests on platforms? With the platforms listed by popularity determined by browser use? Highlight those good folks who do test on MSWin!

        So, hopefully the TODO of CPAN:::Reporter will be to be good enough to allow FAIL reporting on MSWIN Strawberry with no file in the user's home directory.

        I would add, it would be nice if it worked with an HTTP_proxy set in the environment.

        I know, I am whining. Sorry about that, but it is an informed whine.

        Like, let's get POE to install without fail on Wheel on MSWin, before a book comes out on POE. (I can dream, right? The books will be Modern Perl, Moose, and POE, right?)

        • 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