| 1 |
On Fri, Sep 11, 2015 at 5:03 AM, Daniel Campbell <zlg@g.o> wrote: |
| 2 |
> |
| 3 |
> I like the general 'gtk' flag we generally use to choose *which* |
| 4 |
> toolkit, and local USE flags for specific versions, if they are |
| 5 |
> supported. But in that case, the general gtk flag should be |
| 6 |
> interpreted as the latest version supported, so users don't come |
| 7 |
> across weirdly behaving packages that default to gtk2 (unless that |
| 8 |
> version is the most stable). |
| 9 |
> |
| 10 |
>... |
| 11 |
> |
| 12 |
> For starters, versioned USE flags more than likely don't belong in |
| 13 |
> make.conf's USE variable and shouldn't be global. |
| 14 |
> |
| 15 |
|
| 16 |
That was roughly my proposal. |
| 17 |
|
| 18 |
USE=gui or something like that if the main effect is to have a gui or |
| 19 |
not. That is the sort of thing that SHOULD go in make.conf or in a |
| 20 |
profile. If disabling gtk makes it a console-only application then |
| 21 |
use the gui flag. |
| 22 |
|
| 23 |
USE=gtk if the main effect is to select /which/ toolkit is used if |
| 24 |
more than one is optionally supported. That /might/ go in a make.conf |
| 25 |
or profile, but probably shouldn't in general. It is more appropriate |
| 26 |
for something like the desktop/gnome profile than the desktop profile. |
| 27 |
|
| 28 |
USE=gtk# if you're picking which version to use. That should /almost |
| 29 |
never/ go in a profile (unless you're talking about a testing profile |
| 30 |
of some kind, such as on an overlay), or in a global config unless you |
| 31 |
REALLY know what you're getting into. Users setting this globally |
| 32 |
should expect to run into bugs. The package should default these |
| 33 |
flags to whatever is most appropriate for the specific package. |
| 34 |
|
| 35 |
I'd be tempted to even say to not have gtk3 but instead call the flag |
| 36 |
chromium-gtk3 or whatever so that it becomes very difficult to put in |
| 37 |
the global config. However, that goes against our general principle |
| 38 |
of letting the user break their system and keep the pieces if they |
| 39 |
think they know what they're doing. If somebody WANTS to test out a |
| 40 |
gtk3-only system or whatever they should have the freedom to do so, |
| 41 |
understanding that testing sometimes uncovers problems. |
| 42 |
|
| 43 |
Of course any change will need a transition period, news, handbook |
| 44 |
updates, etc. For the person who wants the "just works" experience |
| 45 |
they can pick a profile and it will do the right thing, and if they |
| 46 |
want to tailor things a bit more the USE=(-)gui flag will do what it |
| 47 |
would be expected to do. |
| 48 |
|
| 49 |
-- |
| 50 |
Rich |
Archives