public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Markos Chandras" <hwoarang@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/variables/
Date: Sun, 11 Nov 2012 19:33:34 +0000 (UTC)	[thread overview]
Message-ID: <1352662344.14449d40dcc275f4c113e6e976f1d72671aff7cd.hwoarang@gentoo> (raw)

commit:     14449d40dcc275f4c113e6e976f1d72671aff7cd
Author:     Markos Chandras <hwoarang <AT> gentoo <DOT> org>
AuthorDate: Sat Nov  3 21:59:34 2012 +0000
Commit:     Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Sun Nov 11 19:32:24 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=14449d40

ebuild-writing/variables: Add a note that IUSE must always be present

---
 ebuild-writing/variables/text.xml |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/ebuild-writing/variables/text.xml b/ebuild-writing/variables/text.xml
index 379ca00..f825c06 100644
--- a/ebuild-writing/variables/text.xml
+++ b/ebuild-writing/variables/text.xml
@@ -309,6 +309,9 @@ Note that the <c>IUSE</c> variable is cumulative, so there is no need to specify
 USE flags used only within inherited eclasses within the ebuild's IUSE. Also
 note that it's really really broken in portage versions before 2.0.51.
 </p>
+<important>
+You must always add the IUSE variable in your ebuild even if it is empty.
+</important>
 
 <p>
 Arch USE flags (<c>sparc</c>, <c>mips</c>, <c>x86-fbsd</c> and so on) should not be


             reply	other threads:[~2012-11-11 19:34 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-11 19:33 Markos Chandras [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-24 19:12 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/variables/ Ulrich Mueller
2013-05-15 13:17 Dirkjan Ochtman
2013-05-15 13:39 Dirkjan Ochtman
2013-05-15 13:39 Dirkjan Ochtman
2015-08-07  5:08 Mike Frysinger
2015-12-08 20:06 Ulrich Müller
2016-05-04  9:13 Göktürk Yüksek
2016-05-11  1:43 Mike Gilbert
2016-05-18  6:56 Göktürk Yüksek
2016-05-20  6:23 Göktürk Yüksek
2016-07-13  2:48 Göktürk Yüksek
2016-07-13  3:18 Göktürk Yüksek
2016-10-28 14:21 Göktürk Yüksek
2016-10-28 14:21 Göktürk Yüksek
2016-11-17  5:23 Göktürk Yüksek
2016-12-07 19:46 Göktürk Yüksek
2017-09-09  3:43 Göktürk Yüksek
2017-11-12 20:15 Ulrich Müller
2018-10-24 13:01 Brian Evans
2018-10-24 13:01 Brian Evans
2019-03-19 17:11 Brian Evans
2019-03-19 17:11 Brian Evans
2019-03-24 16:48 Ulrich Müller
2019-05-22 19:40 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-10-16 20:16 Göktürk Yüksek
2019-11-26  1:49 Göktürk Yüksek
2019-11-26  1:49 Göktürk Yüksek
2019-11-28 18:32 Göktürk Yüksek
2019-11-28 18:32 Göktürk Yüksek
2019-11-29  9:28 Ulrich Müller
2020-03-11 14:38 Ulrich Müller
2021-03-26 19:05 Ulrich Müller
2021-03-30  7:21 Ulrich Müller
2021-03-30  7:21 Ulrich Müller
2021-03-30  7:21 Ulrich Müller
2021-03-30  7:21 Ulrich Müller
2021-03-30  7:21 Ulrich Müller
2021-05-28 13:09 Ulrich Müller
2022-02-16 18:02 Matthew Smith
2022-02-16 18:43 Ulrich Müller
2022-02-18 18:19 Sam James
2022-08-25 16:42 Ulrich Müller
2022-08-25 16:42 Ulrich Müller
2022-08-25 16:42 Ulrich Müller
2025-07-22 22:25 James Le Cuirot
2025-07-22 22:25 James Le Cuirot
2025-08-03 13:01 James Le Cuirot
2025-08-03 13:01 James Le Cuirot
2025-09-20 13:24 Sam James

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=1352662344.14449d40dcc275f4c113e6e976f1d72671aff7cd.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