From: "Rolf Eike Beer" <eike@sf-mail.de>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/tatt:master commit in: templates/
Date: Tue, 29 Jun 2021 16:23:10 +0000 (UTC) [thread overview]
Message-ID: <1624893138.5b0d77c02b3bf855fc6117f7ac736f3462694aeb.dakon@gentoo> (raw)
commit: 5b0d77c02b3bf855fc6117f7ac736f3462694aeb
Author: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
AuthorDate: Mon Jun 28 15:09:10 2021 +0000
Commit: Rolf Eike Beer <eike <AT> sf-mail <DOT> de>
CommitDate: Mon Jun 28 15:12:18 2021 +0000
URL: https://gitweb.gentoo.org/proj/tatt.git/commit/?id=5b0d77c0
tatt_functions.sh: keep original use flags when doing initial minimal build
Otherwise missing python_targets_* or ruby_targets_* may cause the build to fail
early.
Signed-off-by: Rolf Eike Beer <eike <AT> sf-mail.de>
templates/tatt_functions.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/templates/tatt_functions.sh b/templates/tatt_functions.sh
index bd21e46..d4e7cdf 100644
--- a/templates/tatt_functions.sh
+++ b/templates/tatt_functions.sh
@@ -49,7 +49,7 @@ function tatt_test_pkg
# Do a first pass to avoid circular dependencies
# --onlydeps should mean we're avoiding (too much) duplicate work
- USE="minimal -doc" emerge --onlydeps -q1 --with-test-deps ${TATT_EMERGEOPTS} "${1:?}"
+ USE="${USE} minimal -doc" emerge --onlydeps -q1 --with-test-deps ${TATT_EMERGEOPTS} "${1:?}"
if ! emerge --onlydeps -q1 --with-test-deps ${TATT_EMERGEOPTS} "${1:?}"; then
echo "merging test dependencies of ${1} failed" >> "${TATT_REPORTFILE}"
next reply other threads:[~2021-06-29 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 16:23 Rolf Eike Beer [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-25 3:46 [gentoo-commits] proj/tatt:master commit in: templates/ Sam James
2023-04-25 3:46 Sam James
2021-10-31 22:11 Sam James
2021-07-04 15:43 Rolf Eike Beer
2021-06-17 22:04 Sam James
2021-05-19 16:31 Rolf Eike Beer
2021-03-04 0:26 Sam James
2021-03-04 0:21 Sam James
2021-02-17 3:09 Sam James
2020-01-02 21:00 Rolf Eike Beer
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=1624893138.5b0d77c02b3bf855fc6117f7ac736f3462694aeb.dakon@gentoo \
--to=eike@sf-mail.de \
--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