From: "Markos Chandras" <hwoarang@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/
Date: Sat, 28 Sep 2013 12:19:12 +0000 (UTC) [thread overview]
Message-ID: <1380370657.4eb1dc77d0de1e3902ff5887fddc93129bc4d3e4.hwoarang@gentoo> (raw)
commit: 4eb1dc77d0de1e3902ff5887fddc93129bc4d3e4
Author: Julian Ospald <hasufell <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 28 10:41:13 2013 +0000
Commit: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Sat Sep 28 12:17:37 2013 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=4eb1dc77
common-mistakes: add 'Masking unsupported/broken useflags' section
Bug #483388
---
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 549cb00..3663eea 100644
--- a/ebuild-writing/common-mistakes/text.xml
+++ b/ebuild-writing/common-mistakes/text.xml
@@ -416,6 +416,19 @@ the purpose of this interface, because it is not reliable anymore.
</body>
</subsection>
+<subsection>
+<title>Masking unsupported/broken USE flags</title>
+<body>
+<p>
+Exceptionally, a package may have an unsupported/broken USE flag
+(this can happen with <e>vanilla</e> or <e>custom-cflags</e>).
+Then the USE flag must be masked for that ebuild
+(usually in <e>profiles/base/package.use.mask</e>),
+at least when the ebuild hits the stable branch.
+</p>
+</body>
+</subsection>
+
</body>
</section>
next reply other threads:[~2013-09-28 12:19 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 12:19 Markos Chandras [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-05 7:57 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/common-mistakes/ Ulrich Müller
2024-07-24 14:15 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-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
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=1380370657.4eb1dc77d0de1e3902ff5887fddc93129bc4d3e4.hwoarang@gentoo \
--to=hwoarang@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