On Fri, Sep 26, 2008 at 2:12 PM, Lucas C. Villa Real
<[EMAIL PROTECTED]> wrote:
> On Thu, Sep 25, 2008 at 8:09 PM, Michael Homer <[EMAIL PROTECTED]> wrote:
>> On Fri, Sep 26, 2008 at 10:01 AM, Lucas C. Villa Real
>> <[EMAIL PROTECTED]> wrote:
>>> On Tue, Sep 23, 2008 at 5:46 AM, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
>>>> Clarification:
>>>> Generic flags are defined in Settings/GenericFlags.conf.
>>>> Setting flags you do in Data/DistUseFlags.conf, Settings/UseFlags.conf
>>>> and USE environmental variable.
>>>>
>>>> Flags are parsed and enabled in this order:
>>>> DistUseFlags.conf, Settings/UseFlags.conf, USE environmental variable,
>>>> flags selected by generic flags
>>> As a simple suggestion, I'd rather name GenericFlags.conf
>>> "UseFlagsDatabase.conf", or something similar -- because that's where
>>> we set our "database".
>> No it isn't. At least, I don't think so... "database"?
>
> That's why it was surrounded by quotes. That's where we the
> assignments are done
Yes, that was what I thought you meant. But no, it isn't, it's a
mapping of generic flags. Most flags will not be in it, and most flags
people enable will not be in it. It's a convenience for the sake of
(mostly) qt/gtk/tk/etc and openssl/gnutls/nss, so that which of those
is used when more than one is available isn't just at the whim of the
recipe author (or worse, just fatal for some programs where they're
mutually-exclusive). Most flags will not belong to a generic, because
it just doesn't make sense outside a quite limited number of cases.
Changing the name to something misleadingly broad isn't going to be
clearer.

An overview of the goals behind the generic flags is in this thread:
http://lists.gobolinux.org/pipermail/gobolinux-devel/2008-July/003733.html
-Michael
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel

Reply via email to