| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 09/09/2015 06:47 AM, Alexandre Rostovtsev wrote: |
| 5 |
> On Wed, 2015-09-09 at 09:20 +0200, Paweł Hajdan, Jr. wrote: |
| 6 |
> |
| 7 |
> In chromium's case (a new gtk3-based ui that needs wider testing), |
| 8 |
> a local gtk3 USE flag does make sense. |
| 9 |
> |
| 10 |
> But in general, the gnome team recommends avoiding the gtk3 flag |
| 11 |
> whenever possible. We definitely don't want it to become a global |
| 12 |
> flag. We are trying to avoid the following scenario: |
| 13 |
> |
| 14 |
> (1) Dozens of ebuilds add gtk3 USE flag, and the semantics of the |
| 15 |
> gtk3 flag differ wildly in those ebuilds: (a) build an optional gui |
| 16 |
> that happens to be based on gtk3 (instead of no gui at all); (b) |
| 17 |
> build experimental gtk3-based gui (instead of stable gtk2 gui as |
| 18 |
> recommended by upstream); (c) build recommended gtk3-based gui |
| 19 |
> (instead of legacy gtk2-based gui which is not supported by |
| 20 |
> upstream any more); (d) build widget library and utilities for gtk3 |
| 21 |
> (possibly in parallel with gtk2 widgets and utilities); (e) build |
| 22 |
> widget library and utilities for gtk3 (and disable gtk2 widgets and |
| 23 |
> utilities - without making any effort to allow both gtk2 and gtk3 |
| 24 |
> support in parallel by splitting the package or renaming a few |
| 25 |
> files). (3) Since the flag is used all over the place, some users |
| 26 |
> try to globally enable or disable it, depending on their personal |
| 27 |
> feelings about Adwaita's tab shapes. (4) Since the flag sometimes |
| 28 |
> means "build a gui (instead of no gui at all)" at some point it |
| 29 |
> gets globally enabled in some profile. (5) Users are forced to |
| 30 |
> maintain giant lists of package.use entries to get a usable desktop |
| 31 |
> environment. Unhappiness reigns. |
| 32 |
> |
| 33 |
> In other words, to avoid the scenario that happened during |
| 34 |
> gtk1/gtk2 transition, and which is now starting with qt4/qt5 [1]. |
| 35 |
> |
| 36 |
> [1] |
| 37 |
> https://archives.gentoo.org/gentoo-dev/message/11e3d077e0d9c953597c3d1 |
| 38 |
7f327c6b3 |
| 39 |
> |
| 40 |
> |
| 41 |
How do you propose packages whose upstreams maintain both gtk2 and |
| 42 |
gtk3 builds but don't actively push one over the other be packaged? I |
| 43 |
currently have gtk3 and gtk2 flags, but it defaults to gtk3. Should |
| 44 |
the gtk3 flag actually be just `gtk` to fall in line with the latest |
| 45 |
version, and `gtk2` provide the expected versioned toolkit? |
| 46 |
|
| 47 |
The package in question is a GUI package, so *some* toolkit version |
| 48 |
needs to be chosen. Defaulting to gtk3 falls in line with gnome-team's |
| 49 |
opinions while still offering gtk2 support. I think limiting it to |
| 50 |
*only* gtk3 would be doing our users a disservice. |
| 51 |
|
| 52 |
- -- |
| 53 |
Daniel Campbell - Gentoo Developer |
| 54 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
| 55 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
| 56 |
-----BEGIN PGP SIGNATURE----- |
| 57 |
Version: GnuPG v2 |
| 58 |
|
| 59 |
iQIcBAEBCAAGBQJV8SMpAAoJEAEkDpRQOeFwzUIQAIMq1BjmnMpevMquOQsoQG4p |
| 60 |
uOev7ndC/lyIyV+S0IRyu8QdlVU3iEuMZHDlu6dtz/jJTDTZ6OjC6yQ4NifYd5nE |
| 61 |
O16D5u2+diYqpBkCjXo2evLRSvHhMrLt6lmzXkHjJkE4zC1jH3faI6x0keZIro2N |
| 62 |
QSaY9pMqfnSET45VuQ632NxgbdZPXc4YpvIty0/AHk86uDuU9aZMyRH6ZpiMp7iu |
| 63 |
aGaNyiRXpL1rlRxXD0ppOM6h7gU0MFIAdA1UQqlgbowchX7/T93dBehOXAO3Z38C |
| 64 |
ANLEuqPVOqYLaR0P8VLXYUIlusx1tbAUIBSy7ZIyr1s7gUsgi9IkwAAIObsrhf66 |
| 65 |
oy0MNFS0oiEVrnUYxLyd3XnAKo8XKUFq3ZTn8m41IZKP21fSGyVhmccrhnmXjYv9 |
| 66 |
k1DC0kMjWPOhtO/8/rdZekoJZYOmXE76HMh74YdMca7DP9E2/WEpuu4P9qUs5EVl |
| 67 |
8mjCLZEwTOex96sRt+OiXDxNP0iMA/hllHbdmJsw1BIZhz3wqMi0msUQhmOi2sSt |
| 68 |
SZQD+KwonbTYZmEAq2GV0pyEaLO8nC6jCj+vqfAZlrM/IUPKeKFnElNrbORfVqSp |
| 69 |
ye/cT4ScmPVpmsEZqB+GizNfX4sue21FHnm7RZpJdIZig2dd9Qjn9LSF0gSwKymK |
| 70 |
Zncie7DhlImRSULbsBr4 |
| 71 |
=13Ur |
| 72 |
-----END PGP SIGNATURE----- |
Archives