From: ludo@gnu.org (Ludovic Courtès)
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] allow specifying a required version in GUILE_PROGS
Date: Mon, 14 Oct 2013 23:05:56 +0200 [thread overview]
Message-ID: <87vc0zh8az.fsf@gnu.org> (raw)
In-Reply-To: <CA+XASoVnxBLMQk4=_T39-skh5H5xT98Bb1ENHgxfmk3ecKRT0Q@mail.gmail.com> ("Aleix Conchillo \=\?utf-8\?Q\?Flaqu\=C3\=A9\=22's\?\= message of "Thu, 3 Oct 2013 15:55:27 -0700")
Hi Aleix,
(Second try.)
Aleix Conchillo Flaqué <aconchillo@gmail.com> skribis:
> From 66fdc5ff8c0fea6c285c5de01cd8efc12ba58e02 Mon Sep 17 00:00:00 2001
> From: Aleix Conchillo Flaque <aconchillo@gmail.com>
> Date: Thu, 3 Oct 2013 15:49:07 -0700
> Subject: [PATCH] allow specifying a required version in GUILE_PROGS
>
> * meta/guile.m4: GUILE_PROGS now takes an optional argument to specify a
> required Guile version. By default, it requires Guile >= 2.0. A micro
> version can also be specified (e.g. GUILE_PROGS([2.0.10])).
The patch looks good to me.
> + _guile_prog_version=`$GUILE -c "(display (version))"`
> + _guile_major_version=`$GUILE -c "(display (major-version))"`
> + _guile_minor_version=`$GUILE -c "(display (minor-version))"`
> + _guile_micro_version=`$GUILE -c "(display (micro-version))"`
> +
> + AC_MSG_CHECKING([for Guile version >= $_guile_required_version])
> + _major_version=`echo $_guile_required_version | cut -d . -f 1`
> + _minor_version=`echo $_guile_required_version | cut -d . -f 2`
> + _micro_version=`echo $_guile_required_version | cut -d . -f 3`
> + if test "$_guile_major_version" -ge "$_major_version"; then
> + if test "$_guile_minor_version" -ge "$_minor_version"; then
> + if test -n "$_micro_version"; then
> + if test "$_guile_micro_version" -lt "$_micro_version"; then
> + AC_MSG_ERROR([Guile $_guile_required_version required, but $_guile_prog_version found])
Perhaps error messages should show
$_guile_major_version.$_guile_minor_version.$_guile_micro_version since
that could differ from $_guile_prog_version (for instance in Debian
$_guile_prog_version is something like 2.0.9-deb42.)
For code contributed to Guile, we ask for a copyright assignment to the
FSF. Would that be OK with you? If yes, I can send you the form
off-list, and then we can proceed (you might even be able to avoid snail
mail entirely.)
TIA,
Ludo’.
next prev parent reply other threads:[~2013-10-14 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 22:55 [PATCH] allow specifying a required version in GUILE_PROGS Aleix Conchillo Flaqué
2013-10-14 21:05 ` Ludovic Courtès [this message]
2013-10-14 21:35 ` Aleix Conchillo Flaqué
2013-10-18 21:50 ` Ludovic Courtès
2013-10-19 0:55 ` Aleix Conchillo Flaqué
2013-12-21 21:05 ` Ludovic Courtès
2013-12-22 6:24 ` Aleix Conchillo Flaqué
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vc0zh8az.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=aconchillo@gmail.com \
--cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).