From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 595C0139085 for ; Fri, 27 Jan 2017 16:47:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 972C3E0E1F; Fri, 27 Jan 2017 16:46:57 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4C20DE0C9E for ; Fri, 27 Jan 2017 16:46:57 +0000 (UTC) Received: from localhost (unknown [100.42.103.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: williamh) by smtp.gentoo.org (Postfix) with ESMTPSA id F3869341421 for ; Fri, 27 Jan 2017 16:46:55 +0000 (UTC) Date: Fri, 27 Jan 2017 10:46:32 -0600 From: William Hubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] berkdb and gdbm in global USE defaults Message-ID: <20170127164632.GA15438@whubbs1.gaikai.biz> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <1485503640.22895.2.camel@gentoo.org> <20170127083223.GK42019@gentoo.org> <5fa433b9-5057-b8e4-64f9-27ef2c67c400@gentoo.org> <1485534429.22895.8.camel@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <1485534429.22895.8.camel@gentoo.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Archives-Salt: 5cbb5874-72e8-42cf-a6be-397caf97f41d X-Archives-Hash: 54496529aeca7263e56278c6326d09e7 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 27, 2017 at 06:27:09PM +0200, Mart Raudsepp wrote: > =DChel kenal p=E4eval, 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 > > > wrote: > > > > =DChel kenal p=E4eval, 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. > > > >=20 > > > > 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. > > >=20 > > > 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. > >=20 > > 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 --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAliLeV8ACgkQblQW9DDEZTh7SwCghd8JSw11waHczpEKY8NPk8OK fYEAn0uMBSV3H7MIhPzwEuLp6vyaZ6K5 =gM+O -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi--