public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
Cc: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Clarify wording on self-blockers
Date: Tue, 26 Apr 2011 20:19:17 +0200	[thread overview]
Message-ID: <19895.3237.434300.678486@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20110426183838.7366562d@googlemail.com>

>>>>> On Tue, 26 Apr 2011, Ciaran McCreesh wrote:

>> Portage ignores self-blockers both in DEPEND and RDEPEND.

> Even strong blockers?

No, strongs blockers are honoured in this case. (Which is fine, since
the spec says "A strong block must not be ignored.")

Updated patch (I've added the word "weak") is included below.

> Also, what happens for packages that can't be rebuilt once they're
> installed (e.g. because they screw up and use stuff on / if it's
> there)?

Such packages should be fixed. But if someone really needs a DEPEND
blocker on the ebuild's version itself, he can use EAPI 2 or later and
a strong blocker.

> We've got this weird situation where DEPEND=!!self would prevent you
> from upgrading or downgrading, but wouldn't stop you from rebuilding
> the exact same version. That doesn't seem right.

> It seems weird that we're mandating that a package manager should
> just outright ignore bits of dependency variables. Maybe it would be
> better to mark it as undefined as to whether or not the package
> manager honours such a block (and tell people not to do it), and
> then for the next EAPI figure out the logical meaning and specify
> that?

I don't like adding such "undefined" bits in cases where portage
behaviour is well-defined.

Ulrich


From 5935aa87d46a97a72c8c032728f50a6ecbdf864d 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..f6318d8 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 Weak 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




  reply	other threads:[~2011-04-26 18:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26 17:28 [gentoo-pms] Clarify wording on self-blockers Ulrich Mueller
2011-04-26 17:38 ` Ciaran McCreesh
2011-04-26 18:19   ` Ulrich Mueller [this message]
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.3237.434300.678486@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=ciaran.mccreesh@googlemail.com \
    --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