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: <1643529157.128dff66839fcc5d02bd2b61592eec486919e404.vapier@gentoo> (raw)

commit:     128dff66839fcc5d02bd2b61592eec486919e404
Author:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 30 07:52:37 2022 +0000
Commit:     Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Sun Jan 30 07:52:37 2022 +0000
URL:        https://gitweb.gentoo.org/proj/autotools-wrappers.git/commit/?id=128dff66

autoconf-wrapper: export WANT_AUTOCONF to the full version

When exporting the WANT_AUTOCONF version based on what we picked, use
the full version instead of the short 2.1 or 2.5 values since they may
expand into an unrelated version (since we accept many versions as an
alias to 2.5).  Practically speaking, there shouldn't be a difference,
but this will make things a bit more clear.

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

 ac-wrapper.sh | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/ac-wrapper.sh b/ac-wrapper.sh
index ca23928..6cb436b 100755
--- a/ac-wrapper.sh
+++ b/ac-wrapper.sh
@@ -183,9 +183,8 @@ fi
 if [ -z "${WANT_AUTOCONF}" ] ; then
 	for v in ${vers} ; do
 		auto_ver=${v%:*}
-		want_ver=${v#*:}
 		if [ "${binary}" = "${full_argv0}-${auto_ver}" ] ; then
-			export WANT_AUTOCONF="${want_ver}"
+			export WANT_AUTOCONF="${auto_ver}"
 			break
 		fi
 	done


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

Thread overview: 25+ 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-05-28  3:18 [gentoo-commits] proj/autotools-wrappers:main commit in: / Sam James
2025-02-27  6:51 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=1643529157.128dff66839fcc5d02bd2b61592eec486919e404.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