From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] berkdb and gdbm in global USE defaults
Date: Fri, 27 Jan 2017 23:58:57 +1300 [thread overview]
Message-ID: <20170127235857.3cd9e847@katipo2.lan> (raw)
In-Reply-To: <20170127083223.GK42019@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
On Fri, 27 Jan 2017 09:32:23 +0100
Fabian Groffen <grobian@gentoo.org> wrote:
> I'm interested to hear how other people feel about this.
Yeah. Pretty much my reaction to
Mart Raudsepp <leio@gentoo.org> wrote:
> The maintainer should be giving the choice of both,
> but if only one can be chosen, the maintainer should make the choice
> for you by preferring one of them. Likely gdbm, given berkdb licensing
> saga.
Brought the same question to me:
If the design is intended to force your hand when you have both, what is indeed
the point of a REQUIRED_USE feature at all?
If "choose a useflag for the user" is something that is happening, it should
at least be *visible* to the user that this is happening, not being a silent
decision that didn't allow the user to have any say in the matter.
What if the feature you chose instead, was contrary to the one they wanted?
If anything, I think this is a suggestion that *maybe* we should a way to
specify a mechanism for allowing a default to be chosen from a mutually
exclusive set, and then:
a. Inform the user via pretend output that this automatic conflict reduction
has been performed
b. Define a portage option that disables automatic conflict resolution for
required USE, so users who hate (a) can turn it off.
But as it stands, Mart's suggestion of "Hey, just don't use required use,
decide for the user" stands essentially as a regression against portage itself.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-27 10:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 3:33 [gentoo-dev] berkdb and gdbm in global USE defaults Mike Gilbert
2017-01-27 7:54 ` Mart Raudsepp
2017-01-27 8:32 ` Fabian Groffen
2017-01-27 10:58 ` Kent Fredric [this message]
2017-01-27 11:16 ` Mart Raudsepp
2017-01-27 11:41 ` Mart Raudsepp
2017-01-27 12:01 ` Dirkjan Ochtman
2017-01-27 12:08 ` Kristian Fiskerstrand
2017-01-27 13:14 ` Fabian Groffen
2017-01-27 16:27 ` Mart Raudsepp
2017-01-27 16:46 ` William Hubbs
2017-01-27 16:51 ` Kristian Fiskerstrand
2017-01-27 16:22 ` Mike Gilbert
2017-01-27 16:56 ` Mart Raudsepp
2017-01-27 18:40 ` Matt Turner
2017-01-28 7:12 ` [gentoo-dev] " Duncan
2017-01-27 16:56 ` [gentoo-dev] " Michael Orlitzky
2018-04-07 18:44 ` William Hubbs
2018-04-07 18:55 ` Michael Orlitzky
2018-04-07 19:16 ` William Hubbs
2018-04-07 19:57 ` Lars Wendler
2018-04-07 20:41 ` Matt Turner
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=20170127235857.3cd9e847@katipo2.lan \
--to=kentnl@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