public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mounir Lamouri <volkmar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] USE flags requirements (EAPI-4 ?)
Date: Mon, 31 Aug 2009 20:02:16 +0200	[thread overview]
Message-ID: <4A9C1028.704@gentoo.org> (raw)
In-Reply-To: <8b4c83ad0908301224o2c48c738pd85fe5cda3adcd10@mail.gmail.com>

Nirbheek Chauhan wrote:
> There's also bug 251179[1], which is ugly at first glance, but shows
> that we don't really need an extra variable to control dependencies
> between USE-flags (it *is* after all a dependency).
>
> So, we can either use
>
> use1? ( =${CATEGORY}/${PVR}[use2,use3,use4] )
>
> which will probably require less changes to portage's resolver; or
> something else like
>
> use1? ( use2 use3 use4 )
>
> The latter is unambiguous because it's not a package atom (no / ).
> Either of these will work great when portage gets automatic
> USE-dependency enabling.
>   
Indeed, this is doable but I don't think it's clear enough. In addition,
speaking of PM, it will force it to be able to detect use1? ( use2 ) and
use1? ( cat/pkg ). Speaking of ebuild readability it's also not a good
thing because that's not real a dependency.
If needed, we can put this in IUSE variable actually. I've nothing
against even if I prefer IUSE_REQUIREMENTS because it's clearer: we
define IUSE vars somewhere and how to handle them somewhere else.

--
Mounir



  reply	other threads:[~2009-08-31 12:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30 17:06 [gentoo-dev] [RFC] USE flags requirements (EAPI-4 ?) Mounir Lamouri
2009-08-30 19:17 ` Thomas Anderson
2009-08-30 19:24 ` Nirbheek Chauhan
2009-08-31 18:02   ` Mounir Lamouri [this message]
2009-08-30 20:50 ` Ciaran McCreesh
2009-08-31 10:52   ` Marijn Schouten (hkBst)
2009-08-31 18:15   ` Mounir Lamouri
2009-08-31 18:27     ` Ciaran McCreesh
2009-08-31 20:49       ` dev-random
2009-08-31 21:15         ` Mounir Lamouri
2009-08-31 20:55       ` Mounir Lamouri

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=4A9C1028.704@gentoo.org \
    --to=volkmar@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