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.
  • A module that I need to run a script identically via SSH on all hosts via 'perl -I ~/lib/perl ' command will have to be 5.005_03 compliant, sadly.

    Solaris / SunOS 5.8 aka 8 is still widely deployed and supported, even though Solaris 9 and 10 are out there. Sun provides /usr/bin/perl 5.005_03. [On these systems, we set "alias" for perl56 and perl58 to our locally built perl's - installed if the app uses them.]

    Applications can bring their own copy of perl with them (with DBI bindings or other XS modules), but
    --
    Bill
    # I had a sig when sigs were cool
    use Sig;
    • Solaris / SunOS 5.8 aka 8 is still widely deployed and supported, even though Solaris 9 and 10 are out there. Sun provides /usr/bin/perl 5.005_03.

      I had just started to write Perl in March 1999. If Sun wants to support an eight-and-a-half-years-old versions of Perl, talk to them about updates. Presumably you're paying them $$$ for a reason.

      Honestly, sysadmins are as much the problem here as anything.

      • > I had just started to write Perl in March 1999. If Sun wants to
        support an eight-and-a-half-years-old versions of Perl, talk to them about updates. Presumably you're paying them $$$ for a reason.
        >
        > Honestly, sysadmins are as much the problem here as anything.

        You really should get out more often.

        Many environments/setups demand/require/dictate stable software installations. (Yes, I'm aware of my .sig line.) And this has often nothing to do with anyone in particular being lazy and/or resistant to
        • You just CANNOT go around upgrading components since that may have grave consequences in other parts of the environment.

          ... except, apparently, for my CPAN modules, as evidenced by all of the pissing and moaning about how I'm so irresponsible, so inexperienced, and such a misanthropic bad person because I don't care that new code doesn't run on versions of Perl released last millennium.

          That's the part I don't get. If you don't upgrade software, why complain that the software you're not going to upgra

          • > That's the part I don't get. If you don't upgrade software, why complain that the software you're not going to upgrade to won't run with the software you won't upgrade?

            It's not that hard a scenario. They may not be able to upgrade the system Perl, or install a newer one, but they may want to use CPAN modules, or some software that they use and *can* upgrade, requires CPAN modules.

            (Of course, one problem is that by default e.g. CPAN.pm wants to install the latest and greatest version. Which is good for getting bugs fixed, but a bad idea for features from future kicking you in the groin.)