From: "Arsen Arsenović" <arsen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-build/make/
Date: Sun, 18 Aug 2024 19:44:56 +0000 (UTC) [thread overview]
Message-ID: <1724010236.1cdc74dabf98dce9923045dbddbe340b20fea719.arsen@gentoo> (raw)
commit: 1cdc74dabf98dce9923045dbddbe340b20fea719
Author: Arsen Arsenović <arsen <AT> gentoo <DOT> org>
AuthorDate: Sun Aug 18 19:37:40 2024 +0000
Commit: Arsen Arsenović <arsen <AT> gentoo <DOT> org>
CommitDate: Sun Aug 18 19:43:56 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1cdc74da
dev-build/make: consistently call guile_bump_sources in new guile revs
It seems that I forgot to update this ebuild after refactoring.
Fixes: a35501c8975b (dev-build/make: switch to new guile mechanism)
Signed-off-by: Arsen Arsenović <arsen <AT> gentoo.org>
dev-build/make/make-4.4.1-r100.ebuild | 2 +-
dev-build/make/make-9999.ebuild | 4 ++++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/dev-build/make/make-4.4.1-r100.ebuild b/dev-build/make/make-4.4.1-r100.ebuild
index 190cab823489..a1793d14fe37 100644
--- a/dev-build/make/make-4.4.1-r100.ebuild
+++ b/dev-build/make/make-4.4.1-r100.ebuild
@@ -68,7 +68,7 @@ src_prepare() {
fi
if use guile; then
- guile-single_src_prepare
+ guile_bump_sources
fi
}
diff --git a/dev-build/make/make-9999.ebuild b/dev-build/make/make-9999.ebuild
index 182219be856b..0a9275fbe6af 100644
--- a/dev-build/make/make-9999.ebuild
+++ b/dev-build/make/make-9999.ebuild
@@ -66,6 +66,10 @@ src_prepare() {
if [[ ${PV} == 9999 ]] ; then
eautoreconf
fi
+
+ if use guile; then
+ guile_bump_sources
+ fi
}
pkg_setup() {
next reply other threads:[~2024-08-18 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 19:44 Arsen Arsenović [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-03 1:05 [gentoo-commits] repo/gentoo:master commit in: dev-build/make/ Sam James
2024-04-30 6:42 Sam James
2024-04-22 3:58 Sam James
2024-03-23 8:37 Sam James
2024-03-23 8:37 Sam James
2024-03-23 8:37 Sam James
2024-03-21 2:48 Sam James
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=1724010236.1cdc74dabf98dce9923045dbddbe340b20fea719.arsen@gentoo \
--to=arsen@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