| 1 |
On Tuesday 27 October 2009 00:26:38 Zeerak Waseem wrote: |
| 2 |
> But instead of just giving the user the answer, wouldn't it be more |
| 3 |
> appropriate, as far as understanding useflags and their uses goes, to give |
| 4 |
> users lists of useflags and what they do. Ie a list of base use flags for |
| 5 |
> say, kde, and also what basic useflags to disable, and a suggestion to |
| 6 |
> read the descriptions of the useflags to add what's necessary. As the |
| 7 |
> handbook currently does. I think with the documentation, one should have |
| 8 |
> enough information to assess what useflags are desired for one's system. |
| 9 |
> And then I'd suggest looking at the packages and the need for various use |
| 10 |
> flags individually, if you want to. But the documentation provides basic |
| 11 |
> useflags for running your system. |
| 12 |
> But again, this is just my take on it :-) |
| 13 |
> |
| 14 |
|
| 15 |
No. Handbook doesn't provide information on every useflag. For this you have |
| 16 |
use{.local.,.}desc in PORTDIR/profiles/. And again, if you missread my previous |
| 17 |
post - there's no way to standarize *every* useflag and tell user "flag foo does |
| 18 |
bar". It's developer who should decide on behalf of user what's the best |
| 19 |
configuration. And user has always choice to disable some useflags and create |
| 20 |
his own configuration for his requirements. |
| 21 |
|
| 22 |
-- |
| 23 |
Cheers |
| 24 |
Dawid Węgliński |
Archives