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.

Why is Perl on Mac such a disaster 14 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • One of the issues (and is being discussed in other threads here) is the problem with File::HomeDir requiring the huge and mostly busted Mac::Carbon. CPAN tries to install this because it will use File::HomeDir to decide where to put ".cpan" on platforms where File::HomeDir is available. Unfortunately this ends up putting .cpan in a directory that contains spaces, which tends to break a lot of module tests and compiles, since most tests are written as though unix was the only filesystem, and I also see tha
    --
    Waiting on the Road to Eventually, I lost my Place On Line

    • the huge and mostly busted Mac::Carbon

      Which parts of Mac::Carbon are busted? Just curious. :-)

      • The parts that let you install it :)

        • Actually, even then, it's been fine for most people. It's just a few tests that were busted. Nothing preventing you from installing it.

          • Failing tests prevent you from installing it, unless you are expert enough to know it's safe to force (and know how to force it).

            • Failing tests prevent you from installing it

              Bah.

              • http://matrix.cpantesters.org/?dist=Mac-Carbon+0.81 [cpantesters.org]

                How about tests that stop the tests, and reporting, on other platforms? Why is it being tested on so many platforms when it only applies to Darwin, or maybe I should ask, why is the chart of testing so crowded with useless information?

                • Because they SHOULD be reporting NA, not UNKNOWN

                  • I guess I don't get it.

                    Why is test time used in testing a Mac-specific module on the Linux platform? Why are reports sent, even reports that say "Not Applicable", when we all know it is not applicable? Why are there columns in the (very good) matrix, that report that all testing of a Mac module on Linux, gave a report of not applicable? Do we care whether the columns, except Darwin, are empty or full of "Not Applicable"?

                    I would rather see the columns empty, because the full columns see to me to be a wast

                    • Shouldn’t there be a test for a modure that is only for the Mac OS, and a graceful exit without reporting, when someone tries to test a Mac module on a non-Mac perl?

                      Yes. That is known as an “NA” report. :-)

                      I would rather see the columns empty, because the full columns see to me to be a waste of something.

                      NA reports are not shown in the matrix (at least not by default – the specifics escape me).

                      Why are reports sent, even reports that say “Not Applicable”, when we all kn

                    • We DON'T all know it's not applicable.

                      There's a defined mechanism for modules to say what platforms they do or do not work on, and Mac::Carbon doesn't use it.

                      Mac::Carbon SAYS that it works on Win32 and Linux and everywhere else.

                      How do we tell the difference something that doesn't run the tests at all, or that knows the module doesn't apply?

                    • You're right, as is Alias. I guess I am so used to high quality in perl, I forget that it is not a right. Sorry for the mini-rant.

                      In my own defense, I do contribute in ways that are small in the big picture, but do stretch me.

                    • I think that is why I posted a thread to pudge when he said bah. I see he was there at the start of testing, and after hearing that Mac::Carbon has some testing problems, he might be in the mood to improve it.

                    • Nothing to apologise for, I was just explaining. Everyone’s contributions are small in the big picture, mind you. And of course the quality is not consistent – but some of it will be high. That’s why it’s important to not put up barriers to entry. And chipping away at that pile is how the good stuff rises to the top – which is how you get the high quality stuff you’re seeing.

                      So don’t think what you’re doing is insignificant – at least not more or less th

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