git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Dennis Stosberg <dennis@stosberg.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] configure: Add test for Perl
Date: 06 Jul 2006 06:03:40 -0700	[thread overview]
Message-ID: <868xn67umr.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20060706124025.G325584e9@leonov.stosberg.net>

>>>>> "Dennis" == Dennis Stosberg <dennis@stosberg.net> writes:

Dennis> +	_perl_version=`"$_perl" -e 'require 5.6.0;printf "%vd", $^V'`

perl -V:version gives you the version like:

        version='5.8.6';

nice and eval-able. :)  But you can just rely on the exit status from

        perl -e 'eval { require 5.006; 1 } or exit 1'

which will be good (0) if the perl is new enough, and bad (1) if the perl is
too old.  (Perl4 will really barf and give an error as well, but still
be an exit 1.)

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

  reply	other threads:[~2006-07-06 13:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 12:40 [PATCH 1/3] configure: Add test for Perl Dennis Stosberg
2006-07-06 13:03 ` Randal L. Schwartz [this message]
2006-07-06 13:10 ` Timo Hirvonen
2006-07-06 13:29   ` Dennis Stosberg
2006-07-06 13:58   ` Matthias Lederhofer
2006-07-06 14:17     ` Gerrit Pape
2006-07-06 14:25       ` Dennis Stosberg
2006-07-06 14:27     ` Timo Hirvonen
2006-07-06 15:34       ` Dennis Stosberg
2006-07-07 11:06   ` Petr Baudis
2006-07-07 11:20     ` Junio C Hamano
2006-07-07 11:23     ` Timo Hirvonen
2006-07-06 15:40 ` Alex Riesen
2006-07-06 15:44   ` Dennis Stosberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=868xn67umr.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=dennis@stosberg.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).