From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] berkdb and gdbm in global USE defaults
Date: Fri, 27 Jan 2017 10:46:32 -0600 [thread overview]
Message-ID: <20170127164632.GA15438@whubbs1.gaikai.biz> (raw)
In-Reply-To: <1485534429.22895.8.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]
On Fri, Jan 27, 2017 at 06:27:09PM +0200, Mart Raudsepp wrote:
> Ühel kenal päeval, R, 27.01.2017 kell 13:08, kirjutas Kristian
> Fiskerstrand:
> > On 01/27/2017 01:01 PM, Dirkjan Ochtman wrote:
> > > On Fri, Jan 27, 2017 at 8:54 AM, Mart Raudsepp <leio@gentoo.org>
> > > wrote:
> > > > Ühel kenal päeval, N, 26.01.2017 kell 22:33, kirjutas Mike
> > > > Gilbert:
> > > > > I recently ran into a REQUIRED_USE constraint that required I
> > > > > select
> > > > > between berkdb and gdbm for an email client.
> > > >
> > > > There shouldn't be a REQUIRED_USE constraint that forces you to
> > > > select
> > > > one or the other. 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.
> > >
> > > I'm not sure this makes sense to me. If the package will actually
> > > select one implementation out of a set, it makes sense to me that
> > > the
> > > maintainer for that package makes that choice explicit towards the
> > > user. In that case, setting REQUIRED_USE accordingly seems exactly
> > > right. The maintainer should set a good default, but if the user's
> > > USE
> > > settings are inconclusive in getting to the choice of
> > > implementation,
> > > it's better to whine explicitly than try to guess implicitly what
> > > the
> > > user wanted.
> >
> > I tend to agree with this sentiment, explicit over implicit behavior
> > ensures better debugging ability and security considerations.
I agree, I prefer explicit strongly over implicit.
> It breaks the highly sought after "Gentoo is about choice" mantra.
> In this case, choice to not care and have the best chosen for me.
Actually it doesn't. In this case the user should make a choice rather
than the maintainer silently making a choice behind their back.
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2017-01-27 16:47 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
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 [this message]
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=20170127164632.GA15438@whubbs1.gaikai.biz \
--to=williamh@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