public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/autotools-wrappers:main commit in: /
Date: Sun, 30 Jan 2022 09:24:21 +0000 (UTC)	[thread overview]
Message-ID: <1643529849.185e2e318d5050eb21e6b9d3c84722f56e4505c0.vapier@gentoo> (raw)

commit:     185e2e318d5050eb21e6b9d3c84722f56e4505c0
Author:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 30 08:04:09 2022 +0000
Commit:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Sun Jan 30 08:04:09 2022 +0000
URL:        https://gitweb.gentoo.org/proj/autotools-wrappers.git/commit/?id=185e2e31

autoconf-wrapper: slightly rework handling of 2.1 version alias

The 2.1 alias only ever expanded into the 2.13 version.  Every other
version uses the 2.5 alias, and at this point, seems extremely unlikely
that this will ever change (or that we'd add a new alias set).  Rework
the WANT_AUTOCONF checking logic to rewrite 2.1 to 2.13, and then accept
any non-2.13 version when 2.5 is used.  This will allow us to burn down
the alias logic entirely which will simplify the code nicely.

Signed-off-by: Mike Frysinger <vapier <AT> gentoo.org>

 ac-wrapper.sh | 15 +++++++++++----
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/ac-wrapper.sh b/ac-wrapper.sh
index 6cb436b..4682082 100755
--- a/ac-wrapper.sh
+++ b/ac-wrapper.sh
@@ -108,17 +108,24 @@ if [ -n "${WANT_AUTOCONF}" ] ; then
 		fi
 
 		auto_ver=${v%:*}
-		want_ver=${v#*:}
 		for wx in ${WANT_AUTOCONF} ; do
 			if [ "${wx}" = "latest" ] ; then
 				wx="2.5"
+			elif [ "${wx}" = "2.1" ] ; then
+				wx="2.13"
 			fi
 			if [ -x "${full_argv0}-${wx}" ] ; then
 				binary="${full_argv0}-${wx}"
 				v="x"
-			elif [ "${wx}" = "${want_ver}" ] && [ -x "${full_argv0}-${auto_ver}" ] ; then
-				binary="${full_argv0}-${auto_ver}"
-				v="x"
+			elif [ "${wx}" = "2.5" ] ; then
+				if [ "${auto_ver}" = "2.13" ] ; then
+					# The "2.5" alias accepts every version except 2.13.
+					continue
+				fi
+				if [ -x "${full_argv0}-${auto_ver}" ] ; then
+					binary="${full_argv0}-${auto_ver}"
+					v="x"
+				fi
 			fi
 		done
 		[ "${v}" = "x" ] && break


             reply	other threads:[~2022-01-30  9:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30  9:24 Mike Frysinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-27  6:51 [gentoo-commits] proj/autotools-wrappers:main commit in: / Sam James
2024-06-07 13:27 Sam James
2023-12-24  0:55 Sam James
2022-12-07 20:46 Sam James
2022-11-22 21:20 Sam James
2022-11-22 21:20 Sam James
2022-02-08  2:58 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-30  9:24 Mike Frysinger
2022-01-29 20:35 Mike Frysinger

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=1643529849.185e2e318d5050eb21e6b9d3c84722f56e4505c0.vapier@gentoo \
    --to=vapier@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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