| 1 |
On 25/02/14 18:44, Jeff Horelick wrote: |
| 2 |
> On 25 February 2014 11:32, Ian Stakenvicius <axs@g.o <mailto:axs@g.o>> wrote: |
| 3 |
> |
| 4 |
> On 25/02/14 11:16 AM, Samuli Suominen wrote: |
| 5 |
> |
| 6 |
> > On 25/02/14 18:12, Rich Freeman wrote: |
| 7 |
> >> On Tue, Feb 25, 2014 at 10:27 AM, Mart Raudsepp <leio@g.o |
| 8 |
> <mailto:leio@g.o>> |
| 9 |
> >> wrote: |
| 10 |
> >>> We acknowledge that our policy may not have been perfect but we |
| 11 |
> >>> need time to analyze claims brought up by/to the QA team to |
| 12 |
> >>> construct a proper proposal for a better policy that would |
| 13 |
> >>> satisfy everyone; hopefully in co-operation with a QA team. |
| 14 |
> >> Is there any reason to think that this analysis will come to a |
| 15 |
> >> different conclusion? |
| 16 |
> >> |
| 17 |
> >> I don't see any concerns on the list that weren't addressed |
| 18 |
> >> already. USE=gtk2 means build gtk2 support USE=gtk3 means build |
| 19 |
> >> gtk3 support USE="gtk2 gtk3" means build support for whichever |
| 20 |
> >> version the maintainer thinks is better (which is what USE=gtk |
| 21 |
> >> meant a week ago) |
| 22 |
> |
| 23 |
> > And how does one select 'the best supported GTK+ for this |
| 24 |
> > application, selected by the package's maintainer.' ? I want latest |
| 25 |
> > best supported GTK+ enabled for all of my packages. I can't figure |
| 26 |
> > out the USE combination from those. You can't surely assume every |
| 27 |
> > user to review every single package and decide for himself after |
| 28 |
> > reading hours, days, weeks, if not even months various package |
| 29 |
> > ChangeLogs, NEWS files, and other possible ways upstreams are |
| 30 |
> > communicating with? And how does user know of all the mail that |
| 31 |
> > goes between upstream and package maintainers about what to choose |
| 32 |
> > for distribution? |
| 33 |
> |
| 34 |
> |
| 35 |
> ...? as per above, USE="gtk2 gtk3", in make.conf. No need to read |
| 36 |
> anything or track changelogs or anything else. Enable both in the |
| 37 |
> profile (I'm guessing they'll both probably be enabled by default in |
| 38 |
> the desktop profile or a sub-profile, tbh) and you're done. |
| 39 |
> |
| 40 |
> If you (as a user) want to experiment with the one the maintainer |
| 41 |
> DIDN'T choose, then set a single specific version for that atom in |
| 42 |
> package.use |
| 43 |
> |
| 44 |
> |
| 45 |
> |
| 46 |
> |
| 47 |
> |
| 48 |
> I agree with the USE flags as described by rich0. In many cases, if a |
| 49 |
user is in a GTK2 environment (such as GNOME2, MATE, XFCE, LXDE, etc), |
| 50 |
it becomes a significant pain to make GTK3 apps look attractive. In that |
| 51 |
case, I feel the users would prefer to have the choice and would choose |
| 52 |
gtk2 over gtk3. Granted, this may be a short term fix because some apps |
| 53 |
are moving to GTK3-only, but I think the users are willing to deal with |
| 54 |
that possible annoyance to have their applications look good in their |
| 55 |
chosen environment. |
| 56 |
|
| 57 |
The theming issue is not an argument of anykind, it's an user error if |
| 58 |
he uses deprecated theme w/o support for GTK+-3 toolkit. |
| 59 |
|
| 60 |
And just to mention, Xfce will be going GTK+-3.x, and has preferred |
| 61 |
those for a long time now, ever since gtk-engines-xfce was created for |
| 62 |
GTK+-3 and unique look. |
| 63 |
With Xfce 4.12 release we'll just add legacy USE flag for xfce4-panel to |
| 64 |
run older plugins, rest will go with USE="gtk" to GTK+-3.x as expected. |
Archives