From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: [gentoo-pms] Clarify wording on self-blockers
Date: Tue, 26 Apr 2011 19:28:39 +0200 [thread overview]
Message-ID: <19895.199.249977.167001@a1i15.kph.uni-mainz.de> (raw)
It's not quite clear what a "block on an ebuild" is, so let's clarify
the wording such that it agrees with portage behaviour.
Portage ignores self-blockers both in DEPEND and RDEPEND.
Ulrich
From 4161e17efacbcb58b6a1de9484cfe683c1e74e65 Mon Sep 17 00:00:00 2001
From: Ulrich Mueller <ulm@gentoo.org>
Date: Tue, 26 Apr 2011 19:10:51 +0200
Subject: [PATCH] Clarify wording on self-blockers.
---
dependencies.tex | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/dependencies.tex b/dependencies.tex
index 362f6cc..6ea179c 100644
--- a/dependencies.tex
+++ b/dependencies.tex
@@ -187,7 +187,7 @@ following exceptions:
\begin{compactitem}
\item Blocks on a package provided exclusively by the ebuild do not count. \label{provided-blocks}
-\item Blocks on the ebuild itself do not count.
+\item Blocks on the package version of the ebuild itself do not count.
\end{compactitem}
\featurelabel{bang-strength} There are two strengths of block: weak and strong. A weak block may be
--
1.7.5.rc1
next reply other threads:[~2011-04-26 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 17:28 Ulrich Mueller [this message]
2011-04-26 17:38 ` [gentoo-pms] Clarify wording on self-blockers Ciaran McCreesh
2011-04-26 18:19 ` Ulrich Mueller
2011-04-26 18:25 ` Ciaran McCreesh
2011-04-27 17:40 ` Maciej Mrozowski
2011-04-27 17:46 ` Ciaran McCreesh
2011-04-27 19:09 ` Maciej Mrozowski
2011-04-27 19:24 ` Ciaran McCreesh
2011-04-27 21:34 ` Maciej Mrozowski
2011-05-02 1:41 ` Brian Harring
2011-05-02 12:34 ` Maciej Mrozowski
2011-05-02 13:10 ` Ciaran McCreesh
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=19895.199.249977.167001@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-pms@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