From: George Shapovalov <georges@its.caltech.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Parsable list of all use variables.
Date: Mon, 13 May 2002 15:21:35 -0700 [thread overview]
Message-ID: <200205131521.35434.georges@its.caltech.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0205131320550.29338-100000@lucifer.evil-core.com>
Hi Bob
short update on a situation.
On Monday 13 May 2002 06:31, Bob Phan wrote:
> > This regex handles those cases:
> >
> > ^([a-z0-9]+)[ \t]+-.*
> The problem with that regex is it only strips out the use variables.
This regexp is used by lintool at present to extract a list of use vars out of
use.desc file. This in a sense enforses present format, however this is only
one tool of which I know that actually parses use.desc at this point.
(and BTW, as it works, lintool will just ignore all run-over description
lines, which is fine for the tool but is a bad idea if you want to get hold
on descriptions as well. Thus I think single line per usevar entry should be
enforced).
Also there were/are plans to assign values to usevars, for example:
arch = (ppc|sparc|x86)
gnome = 1.4
So far this was the only addition mentioned, so this will be possible to
accomodate in a single human-readable file by slightly changing the format.
Probably something of the form:
usevar = (list|of|values); description
can do.
However please understand that these are just that - plans, so old format
(usevar - description\n) is now in force and I expect will be for some time.
As far as policy goes, the word was that there isn't real one. Basically it
goes as far as it gets enforced by accepted tools, in this case lintool
(which only checks for "usevar -" part anyway). If your script gets accepted
it becames a new policy ;). However in order for it to be accepted it should
peacefully coexist with lintool, therefore it would be a good idea to consult
lintool code whenever you are uncertain about any USE-related formats).
George
next prev parent reply other threads:[~2002-05-13 22:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 16:06 [gentoo-dev] Parsable list of all use variables Bob Phan
2002-05-09 20:27 ` Francisco Gimeno
2002-05-09 20:50 ` Francisco Gimeno
2002-05-09 17:16 ` Bob Phan
2002-05-09 21:25 ` Francisco Gimeno
2002-05-09 22:13 ` George Shapovalov
2002-05-10 9:47 ` Bob Phan
2002-05-10 19:31 ` George Shapovalov
2002-05-10 16:50 ` Bob Phan
2002-05-10 21:50 ` George Shapovalov
2002-05-11 23:58 ` Karl Trygve Kalleberg
2002-05-13 13:31 ` Bob Phan
2002-05-13 22:21 ` George Shapovalov [this message]
2002-05-13 14:14 ` Bob Phan
2002-05-13 18:19 ` Karl Trygve Kalleberg
2002-05-10 18:10 ` [gentoo-dev] ebuilds & suid question Alastair Nicol
2002-05-10 16:50 ` Grant Goodyear
2002-05-10 8:31 ` [gentoo-dev] Parsable list of all use variables Karl Trygve Kalleberg
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=200205131521.35434.georges@its.caltech.edu \
--to=georges@its.caltech.edu \
--cc=gentoo-dev@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