From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/
Date: Sun, 1 Aug 2021 02:38:47 +0000 (UTC) [thread overview]
Message-ID: <1627785518.3a00a5fc63342e1a2a5e01ce2db232e5d21f2c3f.sam@gentoo> (raw)
commit: 3a00a5fc63342e1a2a5e01ce2db232e5d21f2c3f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 10 02:16:27 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Aug 1 02:38:38 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=3a00a5fc
ebuild-writing/common-mistakes: mention leftover USE flags, inherits
Suggested-by: Joonas Niilola <juippis <AT> gentoo.org> (inherits)
Signed-off-by: Sam James <sam <AT> gentoo.org>
ebuild-writing/common-mistakes/text.xml | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/ebuild-writing/common-mistakes/text.xml b/ebuild-writing/common-mistakes/text.xml
index ce4bc95..1969efe 100644
--- a/ebuild-writing/common-mistakes/text.xml
+++ b/ebuild-writing/common-mistakes/text.xml
@@ -378,6 +378,19 @@ Make sure when you bump a version, the stable KEYWORDS are all marked as
<c>~</c>.
</p>
+</body>
+</subsection>
+<subsection>
+<title>Unused flags and eclass inherits</title>
+<body>
+
+<p>
+Sometimes obsolete USE flags remain in IUSE despite having no function, e.g. a
+dependency may have become mandatory but the USE flag remains in IUSE and *DEPEND.
+Similarly, eclasses often become redundant due to changes in the ebuild, or new EAPIs,
+e.g. <c>eutils.eclass</c> should be obsolete in modern EAPIs. Remember to prune these.
+</p>
+
</body>
</subsection>
<subsection>
next reply other threads:[~2021-08-01 2:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 2:38 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-24 14:15 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/ Ulrich Müller
2022-01-22 23:43 Sam James
2021-12-22 15:38 Ulrich Müller
2021-09-17 9:09 Ulrich Müller
2021-08-14 10:00 Ulrich Müller
2021-08-01 2:43 Sam James
2021-08-01 2:38 Sam James
2021-08-01 2:38 Sam James
2021-08-01 2:38 Sam James
2021-08-01 2:38 Sam James
2021-03-30 18:20 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 18:15 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-21 6:06 Ulrich Müller
2021-02-06 10:35 Ulrich Müller
2017-01-25 5:31 Göktürk Yüksek
2017-01-25 5:31 Göktürk Yüksek
2017-01-21 19:21 Göktürk Yüksek
2016-10-28 17:13 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2014-10-18 17:36 Markos Chandras
2014-05-13 19:32 Ulrich Müller
2013-09-28 12:19 Markos Chandras
2012-12-30 14:21 Julian Ospald
2012-12-04 19:26 Julian Ospald
2012-11-23 18:02 Julian Ospald
2012-11-17 19:00 Markos Chandras
2012-11-11 19:33 Markos Chandras
2012-11-07 13:27 Michael Palimaka
2012-11-07 13:25 Michael Palimaka
2012-08-08 19:20 Markos Chandras
2011-03-09 16:42 Jeremy Olexa
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=1627785518.3a00a5fc63342e1a2a5e01ce2db232e5d21f2c3f.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