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