From: "Markos Chandras" <hwoarang@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/
Date: Sat, 18 Oct 2014 17:40:39 +0000 (UTC) [thread overview]
Message-ID: <1413654013.9f29f77794f9329b6f5f5e1e2478bbefad9a8b6a.hwoarang@gentoo> (raw)
commit: 9f29f77794f9329b6f5f5e1e2478bbefad9a8b6a
Author: Anthony Ryan <anthonyryan1 <AT> gmail <DOT> com>
AuthorDate: Tue Aug 19 21:19:41 2014 +0000
Commit: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Sat Oct 18 17:40:13 2014 +0000
URL: http://sources.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=9f29f777
Document use dependency defaults on this section of the devmanual
---
general-concepts/dependencies/text.xml | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml
index 8586db6..dc95e28 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -447,7 +447,6 @@ In order to use built with use dependencies you must specify <c>EAPI="2"</c>.
Available specifiers are:
</p>
-<p>
<table>
<tr>
<th>Specifier</th>
@@ -466,13 +465,11 @@ Available specifiers are:
<ti>foo must have bar disabled and baz enabled.</ti>
</tr>
</table>
-</p>
<p>
There are also shortcuts for conditional situations:
</p>
-<p>
<table>
<tr>
<th>Compact form</th>
@@ -495,9 +492,25 @@ There are also shortcuts for conditional situations:
<ti><c>bar? ( app-misc/foo[-bar] ) !bar? ( app-misc/foo[bar] )</c></ti>
</tr>
</table>
+
+<subsection>
+<title>Use dependency defaults</title>
+<body>
+
+<p>
+If a dependency is introducing or removing a <c>USE</c> flag in new versions, a use
+dependency default may be used. Appending a <c>(+)</c> or <c>(-)</c> suffix will indicate
+whether the absence of the flag from a particular version should indicate its
+presence or absence.
+</p>
+<p>
+<c>>=dev-libs/boost-1.48[threads(+)]</c> will treat all versions without <c>threads</c> as having it set.
</p>
</body>
+</subsection>
+
+</body>
</section>
<section>
next reply other threads:[~2014-10-18 17:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 17:40 Markos Chandras [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-28 19:36 [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/ Ulrich Müller
2023-09-27 8:30 Ulrich Müller
2022-06-24 9:14 Ulrich Müller
2022-05-27 9:00 Ulrich Müller
2022-05-22 6:37 Joonas Niilola
2022-05-22 6:37 Joonas Niilola
2022-02-21 5:22 Sam James
2022-02-21 5:22 Sam James
2021-10-19 9:27 Mike Frysinger
2021-10-13 13:42 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-29 20:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2021-03-11 12:44 Ulrich Müller
2020-05-25 15:43 Ulrich Müller
2020-05-25 15:43 Ulrich Müller
2020-01-29 7:59 Ulrich Müller
2020-01-29 7:59 Ulrich Müller
2020-01-29 7:59 Ulrich Müller
2020-01-23 7:47 Ulrich Müller
2019-12-21 5:19 Ulrich Müller
2019-10-16 18:49 Göktürk Yüksek
2018-09-10 15:20 Mike Gilbert
2017-09-25 4:31 Göktürk Yüksek
2017-09-25 4:31 Göktürk Yüksek
2017-09-25 4:31 Göktürk Yüksek
2013-07-29 21:53 Julian Ospald
2013-07-29 21:53 Julian Ospald
2011-02-17 21:08 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=1413654013.9f29f77794f9329b6f5f5e1e2478bbefad9a8b6a.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