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 23:15:55 +0200	[thread overview]
Message-ID: <4A9C3D8B.4020903@gentoo.org> (raw)
In-Reply-To: <20090831204934.GA828@laptop>

dev-random@mail.ru wrote:
> On Mon, Aug 31, 2009 at 07:27:32PM +0100, Ciaran McCreesh wrote:
>   
>> Then when the user turns on all three:
>>
>>     * If 'd' is enabled, if 'a' is enabled, 'b' must not be enabled
>>     * If 'd' is enabled, if 'a' is enabled, 'c' must not be enabled
>>     * If 'd' is enabled, if 'b' is enabled, 'a' must not be enabled
>>     * If 'd' is enabled, if 'b' is enabled, 'c' must not be enabled
>>     * If 'd' is enabled, if 'c' is enabled, 'a' must not be enabled
>>     * If 'd' is enabled, if 'c' is enabled, 'b' must not be enabled
>>
>> And in the general case, there's no way of translating the latter into
>> the former.
>>
>> Much easier for everyone if you just say what you mean rather than
>> converting it into some convoluted (but theoretically equivalent) less
>> expressive syntax.
>>     
>
> I suggest alternative syntax, less powerfull but more expressive:
> groups of use-flags.
>
> Guess we define the following flags in IUSE:
> 3d.nvidia 3d.ati 3d.intel
> or
> 3d+nvidia 3d+ati 3d+intel
> or
> 3d:nvidia 3d:ati 3d:intel
>
> In first case we may enable any number of those flags.
> In second case we must enable at least one of them.
> In third case we must enable exactly one of them.
> In all 3 cases, if (and only if) flag '3d' itself exist in IUSE,
> those flags are ignored when it is unset.
>
> For convenience, user may use '.' as middle-character in config in
> all 3 cases (or, perhaps, even omit it and everything before it),
> but in output of PM he will see proper character and understand
> dependencies between flags without any explanation in English.
>
> If we add flag which depends on nvidia (e.g. cg), we name it
> 3d.nvidia.cg, and it will be ignored (perhaps with warning) if flag
> 3d.nvidia is unset
As you said, it's not enough powerful. It's going to be hard if foo
flags depends on 3d and bar.
In addition, I don't think the real issues is the friendliness of the
syntax but the powerful aspect. Indeed, it shouldn't be shown to the
user and more the syntax is powerful less the user will be annoyed.

--
Mounir



  reply	other threads:[~2009-08-31 16:07 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
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 [this message]
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=4A9C3D8B.4020903@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