From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/pkgcraft/
Date: Mon, 25 Sep 2023 04:05:25 +0000 (UTC) [thread overview]
Message-ID: <1695614613.eb6d4b01b2aa705c36158d49aa4f720906d55ae7.sam@gentoo> (raw)
commit: eb6d4b01b2aa705c36158d49aa4f720906d55ae7
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Sep 25 04:03:15 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Sep 25 04:03:33 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eb6d4b01
sys-libs/pkgcraft: respect USE=debug properly
... or try to, at least. I still feel like this is so easy to get wrong
(and I keeo doing it).
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../pkgcraft/{pkgcraft-0.0.11.ebuild => pkgcraft-0.0.11-r1.ebuild} | 4 +++-
sys-libs/pkgcraft/pkgcraft-9999.ebuild | 4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/sys-libs/pkgcraft/pkgcraft-0.0.11.ebuild b/sys-libs/pkgcraft/pkgcraft-0.0.11-r1.ebuild
similarity index 92%
rename from sys-libs/pkgcraft/pkgcraft-0.0.11.ebuild
rename to sys-libs/pkgcraft/pkgcraft-0.0.11-r1.ebuild
index f839051b1542..544df0ae2420 100644
--- a/sys-libs/pkgcraft/pkgcraft-0.0.11.ebuild
+++ b/sys-libs/pkgcraft/pkgcraft-0.0.11-r1.ebuild
@@ -54,6 +54,7 @@ src_compile() {
--library-type=cdylib
--prefix=/usr
--libdir="/usr/$(get_libdir)"
+ $(usev !debug '--release')
)
# For scallop building bash
@@ -71,7 +72,7 @@ src_test() {
# Need nextest per README (separate processes required)
# Invocation from https://github.com/pkgcraft/pkgcraft/blob/main/.github/workflows/ci.yml#L56
- edo cargo nextest run --color always --all-features
+ edo cargo nextest run $(usev !debug '--release') --color always --all-features --tests
else
# There are no tests for pkgcraft-c. Test via e.g. dev-python/pkgcraft.
:;
@@ -84,6 +85,7 @@ src_install() {
--prefix=/usr
--libdir="/usr/$(get_libdir)"
--destdir="${ED}"
+ $(usev !debug '--release')
)
edo cargo cinstall "${cargoargs[@]}"
diff --git a/sys-libs/pkgcraft/pkgcraft-9999.ebuild b/sys-libs/pkgcraft/pkgcraft-9999.ebuild
index f839051b1542..544df0ae2420 100644
--- a/sys-libs/pkgcraft/pkgcraft-9999.ebuild
+++ b/sys-libs/pkgcraft/pkgcraft-9999.ebuild
@@ -54,6 +54,7 @@ src_compile() {
--library-type=cdylib
--prefix=/usr
--libdir="/usr/$(get_libdir)"
+ $(usev !debug '--release')
)
# For scallop building bash
@@ -71,7 +72,7 @@ src_test() {
# Need nextest per README (separate processes required)
# Invocation from https://github.com/pkgcraft/pkgcraft/blob/main/.github/workflows/ci.yml#L56
- edo cargo nextest run --color always --all-features
+ edo cargo nextest run $(usev !debug '--release') --color always --all-features --tests
else
# There are no tests for pkgcraft-c. Test via e.g. dev-python/pkgcraft.
:;
@@ -84,6 +85,7 @@ src_install() {
--prefix=/usr
--libdir="/usr/$(get_libdir)"
--destdir="${ED}"
+ $(usev !debug '--release')
)
edo cargo cinstall "${cargoargs[@]}"
next reply other threads:[~2023-09-25 4:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 4:05 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-03 17:26 [gentoo-commits] repo/gentoo:master commit in: sys-libs/pkgcraft/ Sam James
2025-01-28 12:21 Sam James
2024-12-09 5:49 Sam James
2024-12-07 2:15 Sam James
2024-08-14 20:07 Sam James
2024-06-23 1:13 Sam James
2024-03-02 1:29 Sam James
2024-02-16 1:26 Sam James
2024-02-02 4:33 Sam James
2023-11-12 4:24 Sam James
2023-09-30 0:44 Sam James
2023-09-25 4:14 Sam James
2023-09-06 19:43 Sam James
2023-06-23 22:45 Sam James
2023-04-25 20:57 Sam James
2023-02-19 19:31 Sam James
2023-02-08 21:41 Sam James
2023-02-05 18:29 Sam James
2023-01-26 7:55 Sam James
2023-01-23 4:12 Sam James
2023-01-23 4:12 Sam James
2023-01-23 4:12 Sam James
2023-01-22 6:38 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=1695614613.eb6d4b01b2aa705c36158d49aa4f720906d55ae7.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