| 1 |
Alistair Bush schrieb: |
| 2 |
>> Hi, |
| 3 |
>> |
| 4 |
>> i would like to start a discussion about reducing the amount of |
| 5 |
>> default-enabled USE flags in profiles, especially in inherited basic |
| 6 |
>> profiles. |
| 7 |
> |
| 8 |
> Sounds like a reasonable idea to me, for the base profiles at least. |
| 9 |
|
| 10 |
Sure. If we have a desktop/kde subprofile, noone should complain, if that profile enables kde |
| 11 |
specific USE flags. On the other hand, if i just want a desktop without kde, i dont want to be |
| 12 |
forced to either choose a none-desktop profile and enable many USE flags by hand or using the |
| 13 |
desktop profile and disabling many USE flags by hand. |
| 14 |
|
| 15 |
> |
| 16 |
>> In addition, i see a trend to enabled more more more USE flags (either over |
| 17 |
>> profiles or via IUSE +flag). Whats the reason for forcing a big load of |
| 18 |
>> default enabled USE flags on every user including more dependencies, more |
| 19 |
>> compile time, more wasted disk space and more possible vulnerabilities |
| 20 |
>> except some users, who complain about a missing feature and are not able |
| 21 |
>> to think and enable a USE flag for that feature? |
| 22 |
>> |
| 23 |
> |
| 24 |
> ".... who complain about a enabled feature and are not able to think and |
| 25 |
> disable a USE flag for that feature?" |
| 26 |
> |
| 27 |
> What a couple of changes make.... |
| 28 |
|
| 29 |
I dont mind, if a flag is really usefull and requested by a big majority of the users. But as Gentoo |
| 30 |
is about choice, the minority should be able to easily choose something else, e.g. by a less |
| 31 |
heavyweight profile. If a majority of mplayer users want to be able to play audio files, i dont mind |
| 32 |
to disable it for myself, if i dont want it. But on the other hand shouldnt a handfull of users be |
| 33 |
able to dictate the enabled and disabled USE flags for many other users, which might have a |
| 34 |
different interest. |
| 35 |
|
| 36 |
> |
| 37 |
> It would be nice if we actually documented why they were enabled. Does the |
| 38 |
> use flag enable significant functionality that would otherwise make the software |
| 39 |
> less useful. |
| 40 |
|
| 41 |
Documentation is always usefull. One should also check the additional overhead of the USE flag. |
| 42 |
|
| 43 |
> |
| 44 |
> I believe we should be trying to find a nice 'middle of the road' balance. DE |
| 45 |
> "related" use flags should be enabled in profiles ( unless of coarse they |
| 46 |
> package is already DE related e.g if a kde package has a use flag for kde's |
| 47 |
> sound system, this could be enabled at a package level while a package with a |
| 48 |
> kde use flag should not default enable it.). |
| 49 |
|
| 50 |
I aggree. |
| 51 |
|
| 52 |
|
| 53 |
-- |
| 54 |
Thomas Sachau |
| 55 |
|
| 56 |
Gentoo Linux Developer |
Archives