| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 09/10/2015 01:47 AM, hasufell wrote: |
| 5 |
> On 09/10/2015 08:21 AM, Daniel Campbell wrote: |
| 6 |
>> |
| 7 |
>> For me to not support gtk2 in the spacefm ebuild would be |
| 8 |
>> providing a package inferior to upstream. |
| 9 |
> |
| 10 |
> That sounds like spacefm with gtk3 is lacking anything. It is not. |
| 11 |
> Providing choice for the sake of choice is not always a good idea. |
| 12 |
> |
| 13 |
|
| 14 |
To my knowledge, the gtk3 version of spacefm *did* indeed have less |
| 15 |
functionality, at first. I think they're mostly the same nowadays, |
| 16 |
though. That said, I wasn't saying gtk3 support was lacking. But if |
| 17 |
our package supports less things than upstreams, we're not shipping |
| 18 |
/as complete/ a package. |
| 19 |
|
| 20 |
For cases where either toolkit is unstable or doesn't work, I'm with |
| 21 |
you: things that are unstable should either be clearly marked as such |
| 22 |
or not added to the ebuild at all. But in spacefm's case, upstream |
| 23 |
actively supports both toolkits and respects the user's choice. |
| 24 |
Following suit here is the best idea, simply because we'd be providing |
| 25 |
the same package and not forcing a choice on the user. |
| 26 |
|
| 27 |
If there was something wrong with the gtk2 build -- let's say later on |
| 28 |
gtk2 just goes unmaintained and starts breaking on Gentoo -- then |
| 29 |
absolutely it should be removed. But for now, I think both should be |
| 30 |
supported. |
| 31 |
|
| 32 |
As for USE flag names, personally it doesn't really matter. I wouldn't |
| 33 |
mind switching USE flag names, but as you said, we need consistency. |
| 34 |
But as long as I'm maintainer of a package that gives users options |
| 35 |
between toolkits, I will support them because as long as said toolkit |
| 36 |
works, it's a sane choice that's *worth* supporting. |
| 37 |
|
| 38 |
Of course, that's just my opinion and others are free to discard or |
| 39 |
ridicule it as they see fit. |
| 40 |
|
| 41 |
tldr: If the problem is USE flags, let's talk USE flags. If it's |
| 42 |
supporting more than one toolkit in general, I see no reason not to |
| 43 |
let maintainers use their discretion and not force their hand in |
| 44 |
either direction. |
| 45 |
|
| 46 |
- -- |
| 47 |
Daniel Campbell - Gentoo Developer |
| 48 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
| 49 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |
| 50 |
-----BEGIN PGP SIGNATURE----- |
| 51 |
Version: GnuPG v2 |
| 52 |
|
| 53 |
iQIcBAEBCAAGBQJV8cimAAoJEAEkDpRQOeFw+jEQAIXcL7m+IEhDlt7pM8hQY3Bm |
| 54 |
gTD0QzcDfXRV+wRkx35mhENXxPnT5hW/kxBYriUwfFFgKaG0BV8/Iv3P+J59J24l |
| 55 |
R9QkgeZJ/DnWgTTYLfiY0tiRnua1g8CWTKG9mWRy1oaLKy0WOLnpcn90sBGVKk5O |
| 56 |
qVWZditk16TiDPcbehPZQCUshnM1+INie3ANh2DeNrNJk6Lg2OmwPB5zeg8t70kn |
| 57 |
cbnFEK1kansHVgglBoka/syY3oXrbEATL1xzLIkCCUp64V7+1yT+bwA1K79BJB9z |
| 58 |
SVawPlI8CwaI3jGfT228gUCdyQzOdDa7ES9PHcMFuD5VettrVMdOpQ7Nm4RXIItt |
| 59 |
LdsTGBjuZ2hu3sQRnsQcOLJQTFsWMUr7kMvBPkKwM8t/HDRJ6zfgP7ND8mi+CktE |
| 60 |
rxa5KcbnOV3Kz13YtuS9SD7MdIjr4X/S4FTGhL23DXNGksltZ3+pRPMEHeV25a8l |
| 61 |
opFYW55UK4Des1HK00glkLJTNsXx4Kv9/rSgh6hpATBKf66Ft9yZ7CtqJWx3EesU |
| 62 |
QRfQ2T5PNDl2HNbybXvggQsg+oVnlPTpwRs2B5FlWHZfKxV+c5sWPtHPsxHpclw/ |
| 63 |
5W/YfUin5DnxBO8bCTk40rpeq3cTdUJkA2i2F63glCcOhXt2LGwq54uKg4GR6v38 |
| 64 |
nWi5NyH2vOwR5rhaqC5q |
| 65 |
=oW5i |
| 66 |
-----END PGP SIGNATURE----- |
Archives