| 1 |
Paul de Vrieze wrote: |
| 2 |
|
| 3 |
>On Saturday 21 August 2004 21:52, Ciaran McCreesh wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>>On Sat, 21 Aug 2004 16:46:15 -0300 Norberto Bensa |
| 7 |
>> |
| 8 |
>><norberto+gentoo-dev@×××××××××.cx> wrote: |
| 9 |
>>| And when you go to use.local.desc all you see is: |
| 10 |
>>| |
| 11 |
>>| cat/package:flag1 - enables flag1 compilation/support |
| 12 |
>>| |
| 13 |
>>| It doesn't say what flag1 is good for! So you end up Googleing, |
| 14 |
>>| etc... |
| 15 |
>> |
| 16 |
>>You might want to file bugs for these... Updating use{,.local}.desc |
| 17 |
>>doesn't take particularly long, and a good description can save users a |
| 18 |
>>lot of time. |
| 19 |
>> |
| 20 |
>> |
| 21 |
> |
| 22 |
>The problem is that many "even official global useflags" would sometimes |
| 23 |
>require package-level descriptions on their effect. Maybe this should be |
| 24 |
>put in the ebuild itself. |
| 25 |
> |
| 26 |
>Paul |
| 27 |
> |
| 28 |
> |
| 29 |
> |
| 30 |
I agree with you. I would like something as `configure --help` for |
| 31 |
example `emerge -useflag foo`, portage parse USE description from the |
| 32 |
ebuild and output something similar to `configure --help`. |
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
Tuan Van |
| 37 |
Gentoo Net-Mail Team |
| 38 |
GnuPG key: 6476B2FD |
| 39 |
Key server: pgp.mit.edu |
| 40 |
Fingerprint: 4CB6 83BD 32D1 BE77 FD14 400B D962 CD73 6476 B2FD |
Archives