| 1 |
A user asked for optional gtk3 support in www-client/chromium: |
| 2 |
<https://bugs.gentoo.org/show_bug.cgi?id=559378> |
| 3 |
|
| 4 |
However, reading e.g. |
| 5 |
<https://wiki.gentoo.org/wiki/Project:GNOME/Gnome_Team_Ebuild_Policies#gtk3> |
| 6 |
says this: |
| 7 |
|
| 8 |
> having USE=gtk3 to enable gtk+-3 instead of gtk+-2 support is |
| 9 |
> forbidden |
| 10 |
|
| 11 |
> package is an application with support for multiple gtk+, maintainer |
| 12 |
> is free to select whatever slot he desires to support. It is strongly |
| 13 |
> advised to use gtk+-3 if functionality is equivalent. This is to |
| 14 |
> reduce workload of bugs being triggered with one slot but not the |
| 15 |
> other. |
| 16 |
|
| 17 |
What are your recommendations for the best course of action? |
| 18 |
|
| 19 |
For stability and maintainability, I'd prefer www-client/chromium to use |
| 20 |
the upstream defaults (gtk+-2 AFAIK) since it's most common, tested, and |
| 21 |
supported configuration. If/when upstream moves to gtk+-3, we'd just follow. |
| 22 |
|
| 23 |
I also understand we have users who are eager to run various |
| 24 |
configurations, and expect Gentoo to be flexible and allow that. Would |
| 25 |
masking a gtk3 USE flag for www-client/chromium be acceptable? Are there |
| 26 |
any other solutions that might work? |
| 27 |
|
| 28 |
Paweł |
Archives