| 1 |
On Sun, 12 Feb 2006 17:49:26 +0100 |
| 2 |
Simon Stelling <blubb@g.o> wrote: |
| 3 |
|
| 4 |
> R Hill wrote: |
| 5 |
> > a global USE flag duplicated in use.local.desc could be used to |
| 6 |
> > give specific information about exactly what effect the flag has on |
| 7 |
> > a certain package, or if for some reason it does differ slightly |
| 8 |
> > from the global meaning. |
| 9 |
> > |
| 10 |
> > global use flags (searching: doc) |
| 11 |
> > ************************************************************ |
| 12 |
> > [- ] doc - Adds extra documentation (API, Javadoc, etc) |
| 13 |
> > |
| 14 |
> > local use flags (searching: doc) |
| 15 |
> > ************************************************************ |
| 16 |
> > [- ] doc (app-examples/fakeapp): |
| 17 |
> > Build user manuals in PDF format (requires ps2pdf) |
| 18 |
> |
| 19 |
> That'd be bad practice. When a new global use flag is made, the |
| 20 |
> requirement is that all local use flags which would get united have |
| 21 |
> *the same meaning*. If the meaning is the same, it doesn't make sense |
| 22 |
> to mention it twice. If the meaning differs (slightly or not), it |
| 23 |
> should get a local use flag. |
| 24 |
|
| 25 |
IIRC the idea behind duplication was not to use a flag for different |
| 26 |
purposes, but have a generic description in use.desc (like "doc: build |
| 27 |
additional docs") and give a more detailed description in |
| 28 |
use.local.desc (like "doc: build API docs and manual as pdf and html"). |
| 29 |
See http://thread.gmane.org/gmane.linux.gentoo.portage.devel/618 and |
| 30 |
http://thread.gmane.org/gmane.linux.gentoo.devel/26035 for the original |
| 31 |
threads about this. |
| 32 |
|
| 33 |
-- |
| 34 |
Public Key at http://www.genone.de/info/gpg-key.pub |
| 35 |
|
| 36 |
In the beginning, there was nothing. And God said, 'Let there be |
| 37 |
Light.' And there was still nothing, but you could see a bit better. |
Archives