From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/blake3/
Date: Mon, 11 Nov 2024 17:27:28 +0000 (UTC) [thread overview]
Message-ID: <1731345825.8020ba3fecac01decfe08d0cd179ece07fab68d6.sam@gentoo> (raw)
commit: 8020ba3fecac01decfe08d0cd179ece07fab68d6
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 11 17:23:45 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Nov 11 17:23:45 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8020ba3f
dev-python/blake3: simplify src_unpack
As suggested by mgorny: unconditionally call cargo_src_unpack as it
does the right thing even if there's no crates to unpack, means we don't
do it twice.
Bug: https://bugs.gentoo.org/943230
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/blake3/blake3-0.4.1-r1.ebuild | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/dev-python/blake3/blake3-0.4.1-r1.ebuild b/dev-python/blake3/blake3-0.4.1-r1.ebuild
index 81a5bb4bf3d8..56a207480f01 100644
--- a/dev-python/blake3/blake3-0.4.1-r1.ebuild
+++ b/dev-python/blake3/blake3-0.4.1-r1.ebuild
@@ -113,8 +113,9 @@ pkg_setup() {
}
src_unpack() {
- default
- use rust && cargo_src_unpack
+ # Do this unconditionally as it has sensible behaviour even
+ # w/ USE=-rust.
+ cargo_src_unpack
}
src_prepare() {
next reply other threads:[~2024-11-11 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 17:27 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-25 6:24 [gentoo-commits] repo/gentoo:master commit in: dev-python/blake3/ Michał Górny
2025-01-14 6:59 Michał Górny
2025-01-04 9:30 Michał Górny
2024-11-30 6:52 Michał Górny
2024-11-11 13:00 Sam James
2024-06-13 19:18 Michał Górny
2024-02-05 3:52 Michał Górny
2024-02-02 13:24 Michał Górny
2023-12-30 18:26 Michał Górny
2023-12-12 16:27 Michał Górny
2023-12-12 16:27 Michał Górny
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=1731345825.8020ba3fecac01decfe08d0cd179ece07fab68d6.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