From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-shells/bashdb/
Date: Thu, 09 Jan 2025 10:21:51 +0000 (UTC) [thread overview]
Message-ID: <1736418093.4f03a72e120646885097d428aa87afb1e6de1da7.sam@gentoo> (raw)
commit: 4f03a72e120646885097d428aa87afb1e6de1da7
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 9 10:21:08 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jan 9 10:21:33 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4f03a72e
app-shells/bashdb: avoid BASH_* var name
It gets stripped from the environment.
Closes: https://bugs.gentoo.org/947766
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-shells/bashdb/bashdb-5.1_pre20240617.ebuild | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/app-shells/bashdb/bashdb-5.1_pre20240617.ebuild b/app-shells/bashdb/bashdb-5.1_pre20240617.ebuild
index 2468ebc8a2a9..299fe8ca9828 100644
--- a/app-shells/bashdb/bashdb-5.1_pre20240617.ebuild
+++ b/app-shells/bashdb/bashdb-5.1_pre20240617.ebuild
@@ -4,12 +4,12 @@
EAPI=8
# Set to 1 for older versions of bash (that are hence slotted)
-BASH_IS_SLOTTED=1
+SLOTTED_BASH=1
-if [[ ${BASH_IS_SLOTTED} == 1 ]] ; then
- BASH_SLOT="${PV:0:3}"
+if [[ ${SLOTTED_BASH} == 1 ]] ; then
+ MANGLED_PV="${PV:0:3}"
else
- BASH_SLOT="0"
+ MANGLED_PV="0"
fi
MY_P="${PN}-${PV:0:3}-${PV:4}"
DESCRIPTION="bash source code debugging"
@@ -36,7 +36,7 @@ LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~amd64 ~ppc ~ppc64 ~x86"
-DEPEND=">=app-shells/bash-${BASH_SLOT}:${BASH_SLOT}"
+DEPEND=">=app-shells/bash-${MANGLED_PV}:${MANGLED_PV}"
RDEPEND="${DEPEND}"
# test-bug-loc fails with formatting differences
@@ -53,8 +53,8 @@ src_prepare() {
src_configure() {
local bash_suffix
- if [[ ${BASH_IS_SLOTTED} == 1 ]] ; then
- bash_suffix="-${BASH_SLOT}"
+ if [[ ${SLOTTED_BASH} == 1 ]] ; then
+ bash_suffix="-${MANGLED_PV}"
fi
# This path matches the bash sources. If we ever change bash,
next reply other threads:[~2025-01-09 10:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 10:21 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-25 7:56 [gentoo-commits] repo/gentoo:master commit in: app-shells/bashdb/ Sam James
2025-01-09 0:28 Sam James
2025-01-09 0:28 Sam James
2025-01-09 0:28 Sam James
2025-01-09 0:08 Sam James
2025-01-09 0:08 Sam James
2024-07-01 18:55 Mike Gilbert
2021-06-16 18:11 Lars Wendler
2020-05-13 13:19 Agostino Sarubbo
2020-05-08 17:13 Agostino Sarubbo
2020-05-06 7:01 Sergei Trofimovich
2020-05-04 15:28 Agostino Sarubbo
2020-05-03 13:07 Thomas Deutschmann
2020-05-01 13:23 Thomas Deutschmann
2019-10-16 11:19 Lars Wendler
2019-10-16 11:19 Lars Wendler
2019-10-03 8:14 Agostino Sarubbo
2019-10-03 8:12 Agostino Sarubbo
2019-10-02 19:08 Agostino Sarubbo
2019-10-02 18:53 Agostino Sarubbo
2018-12-22 19:22 Thomas Deutschmann
2018-11-14 21:58 Thomas Deutschmann
2017-09-17 2:18 Thomas Deutschmann
2016-12-07 8:18 Mike Frysinger
2016-12-07 8:18 Mike Frysinger
2016-12-06 22:24 Patrice Clement
2016-12-06 22:24 Patrice Clement
2016-04-27 9:03 Patrice Clement
2016-04-27 9:03 Patrice Clement
2015-10-16 7:47 Patrice Clement
2015-08-30 20:47 Patrice Clement
2015-08-30 20:47 Patrice Clement
2015-08-30 20:47 Patrice Clement
2015-08-30 20:47 Patrice Clement
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=1736418093.4f03a72e120646885097d428aa87afb1e6de1da7.sam@gentoo \
--to=sam@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