use Perl

• perlgcc (Score:1)

  by thinc (3788)

  Mabye you could try pointing them to perlgcc?
  
  http://use.perl.org/~thinc/journal/30000 [perl.org]
  • Re: (Score:2)

    by jdavidb (1361)

    Thanks! I knew the guy from Sun (Alan Burlison) had done something to make this easier, but I didn't know what.

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
• My point exactly (Score:1)

  by clscott (4354)

  I recently wrote a post at perlmonks advocating why you should always install your own perl [perlmonks.org] and how you may run into issues with a vendor perl with a complex perl application.

  You've been able to shed a bit more light on why it's necessary, thanks for taking the time to write this out so eloquently.
  • Re: (Score:2)

    by jdavidb (1361)

    Thank you. I'm glad to hear that my ideas were helpful, and even more glad just to hear someone say, "I agree," so I know I'm not crazy. :) Also, I appreciate your comment in your perlmonks post that your deployment should be testable, repeatable, and automatable. That's a large part of what I'm going for here.

    I'm about to post a short followup journal entry to this one that may interest you, too.

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
• *always* install your own perl (Score:2)

  by jhi (318)

  That is the only way to guarantee stability, both for your application(s) and for the vendor's application(s) and operating system.
  
  
  • Re: (Score:2)

    by jdavidb (1361)

    Thanks, Jarkko. Having the endorsement here of a former pumpking is probably the best help I could ask for in making this case to coworkers in the future.

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
• Hmmm (Score:1)

  by Abigail (26)

  It's been a while since I last used Solaris, but I never have encountered the problems you describe. Unlike most of the Linux distros I've worked with, Sun comes a long way of insuring that its own Perl dependent utilities still work if you change the default installation of perl. The main idea being that /usr/bin/perl is a link to someplace else. All the OSses scripts use the path of where /usr/bin/perl links to, leaving the admin free to replace /usr/bin/perl. It won't break any of the OSses scripts.

  A f
  • Re: (Score:2)

    by jdavidb (1361)

    It's been a while since I last used Solaris, but I never have encountered the problems you describe. Unlike most of the Linux distros I've worked with, Sun comes a long way of insuring that its own Perl dependent utilities still work if you change the default installation of perl. The main idea being that /usr/bin/perl is a link to someplace else. All the OSses scripts use the path of where /usr/bin/perl links to, leaving the admin free to replace /usr/bin/perl. It won't break any of the OSses scripts.

    T

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers