public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: pkg_pretend USE validation and VALID_USE alternative
Date: Wed, 31 Mar 2010 04:11:02 -0700	[thread overview]
Message-ID: <20100331111102.GF11663@hrair> (raw)
In-Reply-To: <19379.11335.146404.478975@a1i15.kph.uni-mainz.de>

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

On Wed, Mar 31, 2010 at 01:04:39PM +0200, Ulrich Mueller wrote:
> We already have enough issues with circular dependencies, and I'm
> sceptical about adding additional failures on USE flag conflicts.
> Display a warning, but don't error out.

Solve the cyclical dependency via breaking the use cycle and doing two 
builds of the target instead.

It *does* work.  Now I'm reasonably sure I've since *broken* that 
support in pkgcore since stubbs/myself worked it out (resolver still 
supports it though), but that doesn't mean restoring it is hard.  

Frankly I'd rather see us support these things then have the PM bitch 
at the user or make guesses on the users behalf.

My 2 cents either way- mainly responding since you seem to be ignoring 
that as long as pkg_pretend isn't fricking used, we've got a way to 
break use induced cyclical deps automatically via the PM.

~harring

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-03-31 11:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  9:20 [gentoo-dev] pkg_pretend USE validation and VALID_USE alternative Brian Harring
2010-03-31  9:48 ` [gentoo-dev] Re: [gentoo-council] " Ulrich Mueller
2010-03-31 10:46   ` Brian Harring
2010-03-31 11:04     ` [gentoo-dev] " Ulrich Mueller
2010-03-31 11:11       ` Brian Harring [this message]
2010-03-31 15:38       ` "Paweł Hajdan, Jr."
2010-03-31 11:18     ` [gentoo-dev] Re: [gentoo-council] " Piotr Jaroszyński
2010-04-01 20:44     ` Róbert Čerňanský
2010-04-01 21:51       ` Zac Medico
     [not found] ` <201003312316.23806.ali_bush@gentoo.org>
2010-03-31 10:57   ` Brian Harring
2010-03-31 17:49 ` [gentoo-dev] " Alex Alexander
2010-03-31 19:46   ` Brian Harring
2010-03-31 19:56     ` Ciaran McCreesh
2010-04-01  7:31       ` Brian Harring
2010-04-01  7:41         ` Ciaran McCreesh
2010-04-01  7:56           ` Brian Harring
2010-04-01 10:10             ` Gilles Dartiguelongue
2010-04-01 10:18               ` Brian Harring
2010-04-01 10:42                 ` Gilles Dartiguelongue
2010-04-01 10:59                   ` Brian Harring
2010-04-01 11:23                     ` Ciaran McCreesh
2010-04-01 11:38                       ` Brian Harring
2010-04-01 11:50                         ` Ciaran McCreesh
2010-04-01 10:49             ` Ciaran McCreesh
2010-04-01 11:18               ` Brian Harring
2010-04-01 11:44                 ` Ciaran McCreesh
2010-04-01 17:04                 ` David Leverton
2010-04-01 18:39                   ` Dror Levin
2010-04-01 18:55                     ` Ciaran McCreesh
2010-04-02 22:36                     ` David Leverton

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=20100331111102.GF11663@hrair \
    --to=ferringb@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ulm@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