From: Matt Turner <mattst88@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] berkdb and gdbm in global USE defaults
Date: Sat, 7 Apr 2018 13:41:34 -0700 [thread overview]
Message-ID: <CAEdQ38ECPRBr2gcpn9j0Yp_PmuVHMWhr_Aou4FxQHcm08SEv9Q@mail.gmail.com> (raw)
In-Reply-To: <20180407215743.5a25054b@abudhabi.paradoxon.rec>
On Sat, Apr 7, 2018 at 12:57 PM, Lars Wendler <polynomial-c@gentoo.org> wrote:
> On Sat, 7 Apr 2018 14:16:33 -0500 William Hubbs wrote:
>
>>On Sat, Apr 07, 2018 at 02:55:53PM -0400, Michael Orlitzky wrote:
>>> On 04/07/2018 02:44 PM, William Hubbs wrote:
>>> >
>>> > I'm with floppym on this one. Is there a specific reason we enable
>>> > them globally?
>>>
>>> It's a relic from before we had IUSE defaults.
>>>
>>>
>>> > Since there has been so little discussion on this thread, I will
>>> > start looking at what I need to do to remove these use flags from
>>> > the profiles.
>>>
>>> There's probably a few packages that will need IUSE defaults to avoid
>>> breakage, and everyone else should get fair warning before the flags
>>> are turned off by default.
>>
>>There is the case of packages that optionally use a db back end,
>>and I would argue that those may not need iuse defaults.
>>
>>It could also be argued that having one backend enabled globally is
>>good for consistency, but that would end up leading down a bikeshed
>>path that I'm not sure we should go down. I'm just not sure it makes
>>sense to enable more than one of these backends globally.
>>
>>Thoughts?
>>
>>William
>>
>
> Considering the questionable license situation with latest sys-libs/db
> releases (AGPL), I'd say we should prefer gdbm over berkdb in case we
> want to keep one db backend default enabled.
> IIRC Fedora is even trying to entirely getting rid of berkdb.
Interesting. I wasn't aware of that. Here's a link with more information:
https://bugzilla.redhat.com/show_bug.cgi?id=1361971
prev parent reply other threads:[~2018-04-07 20:42 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
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 [this message]
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=CAEdQ38ECPRBr2gcpn9j0Yp_PmuVHMWhr_Aou4FxQHcm08SEv9Q@mail.gmail.com \
--to=mattst88@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