From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/src_test/
Date: Sun, 3 Jan 2021 13:57:56 +0000 (UTC) [thread overview]
Message-ID: <1609682244.7d12a219103e5951c0c5c25cf12abdc306d29868.ulm@gentoo> (raw)
commit: 7d12a219103e5951c0c5c25cf12abdc306d29868
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 15 10:24:48 2020 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun Jan 3 13:57:24 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=7d12a219
ebuild-writing/functions/src_test: IUSE=test is not required.
Closes: https://bugs.gentoo.org/760051
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
ebuild-writing/functions/src_test/text.xml | 20 +++++---------------
1 file changed, 5 insertions(+), 15 deletions(-)
diff --git a/ebuild-writing/functions/src_test/text.xml b/ebuild-writing/functions/src_test/text.xml
index d214b15..baf0ad6 100644
--- a/ebuild-writing/functions/src_test/text.xml
+++ b/ebuild-writing/functions/src_test/text.xml
@@ -68,21 +68,11 @@ src_test() {
<p>
If the packaged software is equipped with a test suite, it is sensible
-to make the package aware of it. This allows the package manager to
-run the software's unit tests. Packages with a test suite must
-announce the "test" USE flag.
-</p>
-
-<codesample lang="ebuild">
-IUSE="test"
-</codesample>
-
-<p>
-The next important aspect to consider are test-only dependencies, i.e.
-dependencies that are only required to run the test suite. Test-only
-dependencies should be specified in a DEPEND behind a USE flag.
-Please refer to the section on
-<uri link="::general-concepts/dependencies/#Test Dependencies"/>
+to run it. Sometimes the package will need additional dependencies for this,
+i.e., dependencies that are only required to run the test suite. Such test-only
+dependencies should be specified in DEPEND or BDEPEND behind a USE flag;
+often, the <c>test</c> USE flag will be used for this. Please refer to the
+section on <uri link="::general-concepts/dependencies/#Test Dependencies"/>
for more information.
</p>
next reply other threads:[~2021-01-03 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 13:57 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-01 9:55 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/src_test/ Ulrich Müller
2021-08-01 9:51 Ulrich Müller
2021-07-06 8:03 Ulrich Müller
2020-08-28 19:02 Ulrich Müller
2020-08-19 17:32 Ulrich Müller
2017-08-24 19:08 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
2017-08-24 19:02 Göktürk Yüksek
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=1609682244.7d12a219103e5951c0c5c25cf12abdc306d29868.ulm@gentoo \
--to=ulm@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