From: "Piotr Jaroszyński" <peper@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Ulrich Mueller <ulm@gentoo.org>, Brian Harring <ferringb@gmail.com>
Subject: [gentoo-dev] Re: [gentoo-council] pkg_pretend USE validation and VALID_USE alternative
Date: Wed, 31 Mar 2010 13:18:32 +0200 [thread overview]
Message-ID: <s2td77765541003310418w10f311ddh436751142861cf6f@mail.gmail.com> (raw)
In-Reply-To: <20100331104647.GD11663@hrair>
>> | Occasionally, ebuilds will have conflicting USE flags for
>> | functionality. Checking for them and returning an error is not a
>> | viable solution. Instead, you must pick one of the USE flags in
>> | conflict to favour.
>>
>> [1] <http://devmanual.gentoo.org/general-concepts/use-flags/>
>
> I honestly consider the ebuild silently making decisions on the user's
> behalf *worse*. Consider if openoffice silently made decisions like
> that- 4 hours later it'll wind up choosing the option you didn't
> really want and you'll be in a foul mood.
I'm pretty sure it says that because there was no way to fail early
before. And failing in the middle of 300 packages upgrade because some
useflags are in conflict wasn't reasonable.
--
Best Regards
Piotr Jaroszyński
next prev parent reply other threads:[~2010-03-31 11:19 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
2010-03-31 15:38 ` "Paweł Hajdan, Jr."
2010-03-31 11:18 ` Piotr Jaroszyński [this message]
2010-04-01 20:44 ` [gentoo-dev] Re: [gentoo-council] " 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=s2td77765541003310418w10f311ddh436751142861cf6f@mail.gmail.com \
--to=peper@gentoo.org \
--cc=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