commit: eb9ba924567615e02a0e4e9f089ad93326b7a3e8
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sun May 7 18:54:04 2017 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Thu Aug 24 18:57:47 2017 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=eb9ba924
ebuild-writing/.../src_test: Do not suggest blanking src_test()
The only reasonable reason to blank src_test() out would be if the check
or test target represented something completely different from tests.
If the tests are broken, the only proper way to disable them is using
RESTRICT=test, as it clearly indicates that they were explicitly
disabled.
ebuild-writing/functions/src_test/text.xml | 15 ++-------------
1 file changed, 2 insertions(+), 13 deletions(-)
diff --git a/ebuild-writing/functions/src_test/text.xml
b/ebuild-writing/functions/src_test/text.xml
index 3790195..f43fae0 100644
--- a/ebuild-writing/functions/src_test/text.xml
+++ b/ebuild-writing/functions/src_test/text.xml
@@ -107,19 +107,8 @@ suite is extremely helpful for arch maintainers.
<title>Skipping Tests</title>
<body>
<p>
-Sometimes it is necessary to skip tests entirely. This can be done
-using a dummy <c>src_test</c> function:
-</p>
-
-<codesample lang="ebuild">
-src_test() {
- # Tests don't even remotely work inside portage
- true
-}
-</codesample>
-
-<p>
-Another option would be to set <c>RESTRICT="test"</c> in the ebuild.
+Sometimes it is necessary to skip tests entirely. This can be done by
+setting <c>RESTRICT="test"</c> in the ebuild.
</p>
<note>
