From: Simon Stelling <blubb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Duplicated entries in use.desc and use.local.desc
Date: Sun, 12 Feb 2006 17:49:26 +0100 [thread overview]
Message-ID: <43EF6716.7040902@gentoo.org> (raw)
In-Reply-To: <dsno96$rdf$1@sea.gmane.org>
R Hill wrote:
> a global USE flag duplicated in use.local.desc could be used to give specific
> information about exactly what effect the flag has on a certain package, or if
> for some reason it does differ slightly from the global meaning.
>
> global use flags (searching: doc)
> ************************************************************
> [- ] doc - Adds extra documentation (API, Javadoc, etc)
>
> local use flags (searching: doc)
> ************************************************************
> [- ] doc (app-examples/fakeapp):
> Build user manuals in PDF format (requires ps2pdf)
That'd be bad practice. When a new global use flag is made, the requirement is
that all local use flags which would get united have *the same meaning*. If the
meaning is the same, it doesn't make sense to mention it twice. If the meaning
differs (slightly or not), it should get a local use flag.
--
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
blubb@gentoo.org
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-12 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 8:19 [gentoo-dev] Duplicated entries in use.desc and use.local.desc Mark Loeser
2006-02-12 8:27 ` Ciaran McCreesh
2006-02-12 16:38 ` [gentoo-dev] " R Hill
2006-02-12 16:49 ` Simon Stelling [this message]
2006-02-12 18:23 ` Marius Mauch
2006-02-12 19:49 ` Mark Loeser
2006-02-13 3:04 ` Marius Mauch
2006-02-13 3:19 ` Mark Loeser
2006-02-13 7:32 ` Ciaran McCreesh
2006-02-13 3:39 ` R Hill
2006-02-13 4:28 ` Mark Loeser
2006-02-13 6:28 ` R Hill
2006-02-13 10:34 ` Thomas de Grenier de Latour
2006-02-13 10:29 ` Thomas de Grenier de Latour
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=43EF6716.7040902@gentoo.org \
--to=blubb@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