public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Julian Ospald" <julian.ospald@googlemail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/dependencies/
Date: Mon, 29 Jul 2013 21:53:05 +0000 (UTC)	[thread overview]
Message-ID: <1375134731.b4cff9c0030cd3bb41b3248472cd2a134159e0dd.hasufell@gentoo> (raw)

commit:     b4cff9c0030cd3bb41b3248472cd2a134159e0dd
Author:     hasufell <hasufell <AT> posteo <DOT> de>
AuthorDate: Mon Jul 29 21:52:11 2013 +0000
Commit:     Julian Ospald <julian.ospald <AT> googlemail <DOT> com>
CommitDate: Mon Jul 29 21:52:11 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=b4cff9c0

add info about hardblockers wrt #407597

---
 general-concepts/dependencies/text.xml | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/general-concepts/dependencies/text.xml b/general-concepts/dependencies/text.xml
index ce25fa7..587a0d7 100644
--- a/general-concepts/dependencies/text.xml
+++ b/general-concepts/dependencies/text.xml
@@ -208,7 +208,7 @@ asterisk. Also note that when selecting all versions in a specific
 
 <p>
 Sometimes two packages cannot be installed in parallel. This is handled by
-blockers. A blocker is specified as follows:
+blockers. A softblocker is specified as follows:
 </p>
 
 <codesample lang="ebuild">
@@ -216,7 +216,19 @@ RDEPEND="!app-misc/foo"
 </codesample>
 
 <p>
-Note that blockers are usually <e>runtime</e> rather than buildtime.
+Portage will try to resolve this conflict automatically if possible.
+Sometimes we need to use a hardblocker to ensure correct emerge order.
+Those cannot be resolved by Portage and must be taken care of by the user.
+A hardblocker is specified as follows:
+</p>
+
+<codesample lang="ebuild">
+RDEPEND="!!app-misc/foo"
+</codesample>
+
+<p>
+Hardblockers always take precedence over softblockers and need at least EAPI="2".
+Also note that blockers are usually <e>runtime</e> rather than buildtime.
 </p>
 
 <p>


             reply	other threads:[~2013-07-29 21:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 21:53 Julian Ospald [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
2014-10-18 17:40 Markos Chandras
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=1375134731.b4cff9c0030cd3bb41b3248472cd2a134159e0dd.hasufell@gentoo \
    --to=julian.ospald@googlemail.com \
    --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