| 1 |
But instead of just giving the user the answer, wouldn't it be more |
| 2 |
appropriate, as far as understanding useflags and their uses goes, to give |
| 3 |
users lists of useflags and what they do. Ie a list of base use flags for |
| 4 |
say, kde, and also what basic useflags to disable, and a suggestion to |
| 5 |
read the descriptions of the useflags to add what's necessary. As the |
| 6 |
handbook currently does. I think with the documentation, one should have |
| 7 |
enough information to assess what useflags are desired for one's system. |
| 8 |
And then I'd suggest looking at the packages and the need for various use |
| 9 |
flags individually, if you want to. But the documentation provides basic |
| 10 |
useflags for running your system. |
| 11 |
But again, this is just my take on it :-) |
| 12 |
|
| 13 |
On Tue, 27 Oct 2009 01:08:30 +0100, Dawid Węgliński <cla@g.o> wrote: |
| 14 |
|
| 15 |
> On Monday 26 October 2009 21:06:04 Rémi Cardona wrote: |
| 16 |
>> Le 24/10/2009 15:42, Maciej Mrozowski a écrit : |
| 17 |
>> > If you have any comments, suggestions, important notices regarding |
| 18 |
>> this |
| 19 |
>> > change, please keep discussion in gentoo-desktop mailing list. |
| 20 |
>> |
| 21 |
>> IMHO, we shouldn't even have desktop/server subprofiles to begin with. |
| 22 |
>> |
| 23 |
>> I've always considered Gentoo to be an "opt-in" distro where after a |
| 24 |
>> successful install, you end up with a bash prompt and a _means_ of |
| 25 |
>> installing new packages. |
| 26 |
>> |
| 27 |
>> Finding out what USE flags mean and do is part of the Gentoo experience. |
| 28 |
>> If we were doing spin-off distros like Ubuntu and Fedora do, then |
| 29 |
>> subprofiles would be fine, but we're not. |
| 30 |
>> |
| 31 |
> |
| 32 |
> So hmm, let me make few hypothetical statements. You see package |
| 33 |
> foo-libs/baz |
| 34 |
> has USE="pic" that is not set by default in profile. It's well |
| 35 |
> documented in |
| 36 |
> metadata.xml which says "disable optimized assembly code that is not PIC |
| 37 |
> friendly". So as an ordinary user you set it in your make.conf because |
| 38 |
> it may |
| 39 |
> be helpful. Then you want to install another package with USE="pic" but |
| 40 |
> you |
| 41 |
> note this useflag for this package means "Force shared libraries to be |
| 42 |
> built as |
| 43 |
> PIC (this is slower)". Of course you don't want your programs run |
| 44 |
> slower, do |
| 45 |
> you? So you disable useflag in make.conf or package.use. This situation |
| 46 |
> may |
| 47 |
> lead user to reinstall half of his system, because some packages with |
| 48 |
> USE="- |
| 49 |
> pic" force foo-libs/baz[-pic] and foo-libs/bar[-pic] too. You end up with |
| 50 |
> nothing after some time spent on reading metadata.xml, recompilling foo, |
| 51 |
> bar, |
| 52 |
> baz... just because you were forced to have a choice. |
| 53 |
> |
| 54 |
> IMO profiles are very good solution for every user. Especially for those |
| 55 |
> that |
| 56 |
> don't know what every use flag means and they (profiles) should have at |
| 57 |
> least |
| 58 |
> base useflags set. And if base, why not most of useful? They are only |
| 59 |
> option. |
| 60 |
> User can alwasy disable it (eg. -kde if he wants gnome, -gnome if he |
| 61 |
> wants kde |
| 62 |
> or - both if he uses openbox). |
| 63 |
> |
| 64 |
> My $0,02. |
Archives