Re: [Monotone-devel] Contributed scripts and how to handle them...

[CooSoft Support]

What I was referring to as standard Perl, was in the English sense of  
the word and not referring to an ISO standard. I.e. my script will run 
on a basic vanilla install of Perl, what would be got by downloading and 
compiling the tar ball from www.perl.org with default arguments to 
./configure. It doesn't need extra CPAN packages, unlike mtn-browse, and 
is not dependant on multi-threading (an option on ./configure). It's 
just a lot easier to use the word `standard'... :-)

What is available to a Perl script can differ quite dramatically from 
distro to distro. mtn-browse would work out of the box on Mandrake, 
likewise Debian and Ubuntu, but RedHat you would have to download about 
10 CPAN packages. Whereas mtn-cleanup is a much more basic script.

Sorry for the confusion.

Hope this helps :-)

Tony.

Stephen Leake wrote:
> Richard Levitte <address@hidden> writes:
>
>   
> > In message <address@hidden> on Sun, 06 Feb 2011 10:04:35 -0500, Stephen Leake 
> > <address@hidden> said:
> >
> > stephen_leake> I have a beef about people using the word "standard" in this 
> > way; is
> > stephen_leake> there an actual ISO or national standard for Perl? Or do you 
> > just mean
> > stephen_leake> "Perl from some normal place, not customized". We need more 
> > terms for
> > stephen_leake> this. We have "international standard", "national standard", 
> > "industry
> > stephen_leake> standard". I don't think Perl is any of those? It's just a 
> > common package.
> >
> > de-facto standard ;-)
> >     
>
> Hmm. That would be for things like Hayes modem commands, or Midi
> commands; one company initially dominated, then other companies created
> independent implementations of the same command set.
>
> I think there is only one Perl implementation.
>
> So just "Perl" is enough; no need to say "standard".
>
>