| 1 |
Am Wed, 16 Nov 2016 11:25:02 +0000 |
| 2 |
schrieb Jorge Almeida <jjalmeida@×××××.com>: |
| 3 |
|
| 4 |
> On Wed, Nov 16, 2016 at 9:08 AM, Neil Bothwick <neil@××××××××××.uk> |
| 5 |
> wrote: |
| 6 |
> > On Wed, 16 Nov 2016 07:23:02 +0000, Jorge Almeida wrote: |
| 7 |
> > |
| 8 |
> >> |
| 9 |
> > What you're asking is a bit like asking for a complete list of the |
| 10 |
> > abilities the python USE flag adds, when all you can really say is |
| 11 |
> > it allows the software to run Python scripts, not what those |
| 12 |
> > scripts may do. |
| 13 |
> > |
| 14 |
> > |
| 15 |
> I'm not really asking for exhaustive documentation about USE flags, |
| 16 |
> just saying that even some fragmented documentation would be useful. I |
| 17 |
> don't expect a particular contributor to know everything about a |
| 18 |
> particular USE flag. (And, of course, no one is under any obligation |
| 19 |
> to do it.) |
| 20 |
> |
| 21 |
> All this would be easier if upstream package developers would explain |
| 22 |
> what the different config options really entail. Most of the times, |
| 23 |
> "./configure --help" is not that helpful. |
| 24 |
|
| 25 |
One could start a wiki entry for each use flag on the Gentoo wiki. |
| 26 |
|
| 27 |
Also, you can use "euse -i USEFLAGNAME" which is sometimes helpful, |
| 28 |
sometimes not - depending on how generic the description is. |
| 29 |
|
| 30 |
-- |
| 31 |
Regards, |
| 32 |
Kai |
| 33 |
|
| 34 |
Replies to list-only preferred. |
Archives