1 |
hasufell posted on Thu, 10 Sep 2015 17:35:53 +0200 as excerpted: |
2 |
|
3 |
>> Again, I'm saying that maintainers should be free to support multiple |
4 |
>> versions if they wish to do so. They should not be required to do so. |
5 |
>> And yes, I do realize that this limits options for users, but they're |
6 |
>> welcome to proxy-maintain packages that do support the versions they |
7 |
>> wish to use. If they want to fork upstream they're even welcome to do |
8 |
>> that, but obviously that isn't going to happen often. |
9 |
>> |
10 |
>> I just don't think we should be in the business of saying "no" here. |
11 |
> |
12 |
> Again, your proposed use case is 1) imaginary 2) currently impossible to |
13 |
> support, because there are lots of applications which either force gtk3 |
14 |
> in the ebuild or have only gtk3 supported upstream. It will be pretty |
15 |
> much impossible to not have gtk3 installed or loaded into RAM, unless |
16 |
> you don't use a DE in the first place and stick to terminals. |
17 |
|
18 |
Pretty much impossible? For a kde and gtk2-based software user? Not so |
19 |
much. I've only one package here using gtk3, a relatively recent |
20 |
addition to a set in my world-sets file, and it's a rather optional |
21 |
package (solaar, for managing my Logitech wireless devices), with a CLI- |
22 |
only option, so I've been thinking about disabling gtk3 support just to |
23 |
avoid having to hassle the gtk3 and supporting software updates. |
24 |
|
25 |
One thing I learned fairly quickly with gentoo is that unlike binary |
26 |
distros, over time there's a real cost to one-off or two-off |
27 |
dependencies, because they aren't just single-time builds, but are |
28 |
generally updated and must be repeatedly rebuilt over time. For things |
29 |
you /might/ use, or do use occasionally, but only perhaps yearly or less |
30 |
often, it's often more efficient to merge on-demand, then unmerge again, |
31 |
until they happen to be needed again, than it is to keep them and |
32 |
dependencies current the whole time. (Tho obviously, this applies more |
33 |
to ~arch users who do --deep updates, than others.) |
34 |
|
35 |
In that context, given the current usage of gtk3 in-tree, it's quite |
36 |
realistic for a user to wish to avoid gtk3, if they've a number of gtk2- |
37 |
only apps (as I do). Similarly the other way of course, for those with a |
38 |
number of gtk3 apps, they may wish to avoid gtk2 and gtk2-only apps, if |
39 |
they can, to avoid it being on their system, tho AFAIK with both chromium |
40 |
and firefox being gtk2 at this point, that's a bit more difficult. |
41 |
|
42 |
Unfortunately, gentoo/gtk's attitude makes this much more difficult than |
43 |
it should be. |
44 |
|
45 |
-- |
46 |
Duncan - List replies preferred. No HTML msgs. |
47 |
"Every nonfree program has a lord, a master -- |
48 |
and if you use the program, he is your master." Richard Stallman |