public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/
Date: Thu, 23 Jan 2020 07:47:09 +0000 (UTC)	[thread overview]
Message-ID: <1579737661.68aff5730fe3477bfb4f0990008e620964792b92.ulm@gentoo> (raw)

commit:     68aff5730fe3477bfb4f0990008e620964792b92
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 20 20:35:13 2020 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Thu Jan 23 00:01:01 2020 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=68aff573

general-concepts/dependencies: Drop section on if-else USE blocks.

If-else USE blocks, i.e. "Legacy Inverse USE-Conditional Dependency
Syntax", have been abandoned before EAPI was introduced.

Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 general-concepts/dependencies/text.xml | 30 ------------------------------
 1 file changed, 30 deletions(-)

diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml
index 9f2cc47..4e3a84e 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -536,36 +536,6 @@ presence or absence.
 </subsection>
 </section>
 
-<section>
-<title>Legacy Inverse USE-Conditional Dependency Syntax</title>
-<body>
-
-<p>
-	Once upon a time the <c>:</c> conditional operator was allowed in <c>*DEPEND</c>:
-</p>
-
-<codesample lang="ebuild">
-DEPEND="use-flag? ( app-misc/foo ) : ( app-misc/bar )"
-</codesample>
-
-<p>
-<b>This syntax is no longer permitted</b>. It is exactly equivalent to the
-following, which should be used instead:
-</p>
-
-<codesample lang="ebuild">
-DEPEND="use-flag?  ( app-misc/foo )
-	!use-flag? ( app-misc/bar )"
-</codesample>
-
-<p>
-It is useful to recognise the legacy syntax and to know that it is no longer
-valid.
-</p>
-
-</body>
-</section>
-
 <section>
 <title>Test Dependencies</title>
 <body>


             reply	other threads:[~2020-01-23  7:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23  7:47 Ulrich Müller [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
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
2014-10-18 17:40 Markos Chandras
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=1579737661.68aff5730fe3477bfb4f0990008e620964792b92.ulm@gentoo \
    --to=ulm@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