public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] berkdb and gdbm in global USE defaults
Date: Fri, 27 Jan 2017 14:14:08 +0100	[thread overview]
Message-ID: <20170127131408.GM42019@gentoo.org> (raw)
In-Reply-To: <5fa433b9-5057-b8e4-64f9-27ef2c67c400@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]

On 27-01-2017 13:08:41 +0100, Kristian Fiskerstrand wrote:
> > On Fri, Jan 27, 2017 at 9:32 AM, Fabian Groffen <grobian@gentoo.org> wrote:
> >> Replying here because I think said email client is the one I recently
> >> added REQUIRED_USE constraints for.
> >>
> >> Reason I added it is because it greatly simplified the ebuild: it's not
> >> just bdb and gdbm, but also tokyocabinet, qdbm and lmdb, with as result
> >> a lot of if-else-casing which implemented the implicit defaults before.
> >> I didn't realise changing this to REQUIRED_USE resulted in a conflict on
> >> default profiles, because I (obviously) have a package.use entry for the
> >> package.
> > I don't see Mike saying you got it wrong here. Reading your email, I
> > think you did the right thing.
> 
> Yup

That blurb was more directed at Mart ;)  I think I just explained why I
did what I did.  The scenario in older ebuilds (without REQUIRED_USE)
was basically the scenario that Mart suggested to be perferable over the
new REQUIRED_USE scenario.

I'm not looking for wrong/right.  I'm looking for concensus on this
topic, then I will likely change the ebuild to match concensus.

Fabian


-- 
Fabian Groffen
Gentoo on a different level

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-01-27 13:14 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 [this message]
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=20170127131408.GM42019@gentoo.org \
    --to=grobian@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