1 |
On Tue, 2005-03-29 at 12:15 +0200, Fabian Zeindl wrote: |
2 |
> Hello |
3 |
> |
4 |
> There was a discussion on the gentoo-user-de list about this two |
5 |
> Useflags: gtk and gtk2. Because not everybody is sure what the mean, so |
6 |
> if you have -gtk +gtk2 some think that gtk2 should be installed and soon. |
7 |
> |
8 |
> Wouldn't it be better if "gtk" meaned that the newest available gtk |
9 |
> version ist installed (gtk1 or gtk2) and a flag like oldgtk take the |
10 |
> older version gtk1. |
11 |
> |
12 |
> Another question which occured: Is there a performancedrawback if a |
13 |
> program is compile with gtk1 AND gtk2 build in? Does this happen when |
14 |
> someone installs with +gtk +gtk2? |
15 |
|
16 |
|
17 |
Common misconception, it tends to crop up once every 6 months or so |
18 |
since I ever was foolish enough not to stomp a hard policy and beat the |
19 |
people who want gtk+-1.2 support with a sledgehammer. |
20 |
|
21 |
|
22 |
Okay. Here's the deal and the logic: |
23 |
|
24 |
USE="gtk" |
25 |
|
26 |
I want gtk support. Legacy. classic. Doesn't matter if the version |
27 |
is gtk+-1.2 or 2.0. ( When it was introduced, there was only gtk+-1.2, |
28 |
and that was it) |
29 |
|
30 |
Then came a few, troublesome beasts and started to make our days |
31 |
annoying. Mozilla was one of them, gFtp another. Enough of them |
32 |
cropped up that used -both- gtk+-1.2 and gtk+-2 interfaces _AS A |
33 |
TRANSITION PERIOD_ |
34 |
|
35 |
The gtk+-1.2 interfaces were planned to be deprecated when the new and |
36 |
shiney(!) interfaces were usable, and have so been done. |
37 |
|
38 |
|
39 |
The gtk2 USE flag came up for -only- theese packages. Nothing else. |
40 |
|
41 |
Its a mistake, abusing the redundancy that boolean nested flags work |
42 |
with, however, I was young, naive, and expected people to be able to |
43 |
comprehend written instructions and nested logic blocks. |
44 |
|
45 |
DEPEND="gtk? ( |
46 |
gtk2? ( >=x11-libs/gtk+-2.0 ) |
47 |
!gtk2? ( =x11-libs/gtk+-1.2* )) |
48 |
!gtk? ( sys-libs/ncurses )" |
49 |
|
50 |
is obvious and fairly logical in my mind, and is the code that describes |
51 |
what the gtk2 USE flag is for. |
52 |
|
53 |
Along with the following descriptions: |
54 |
|
55 |
gtk - Adds support for x11-libs/gtk+ (The GIMP Toolkit) |
56 |
gtk2 - Use gtk+-2.0.0 over gtk+-1.2 in cases where a program supports |
57 |
both. |
58 |
|
59 |
|
60 |
If someone can suggest a better formulation for this, please go ahead. |
61 |
|
62 |
|
63 |
Lets face it, gtk+-1.2 is _deprecated_ and all packages that use it |
64 |
should either be taken out and shot in the head, ( for mercy's sake, |
65 |
that and utf8 ) or updated to track the new and maintained library |
66 |
API. |
67 |
|
68 |
We all know this isn't feasible, most projects are just recently wiping |
69 |
stale code for interfaces ( Hi mozilla! ) and as such, the mistake is |
70 |
left to stay. |
71 |
|
72 |
-Changing- existing logic is -not- going to solve this solution |
73 |
cleanly. We suggested to remove the gtk2 flag, (make it default) and |
74 |
implement : |
75 |
USE="shoot-me-in-the-head-with-deprecated-libraries-please" instead, |
76 |
however people considered it as offending our users for some reason. |
77 |
|
78 |
|
79 |
|
80 |
As for the discussion of USE="-gtk +gtk2" : |
81 |
|
82 |
there is one case where this could be a acceptable and will produce |
83 |
expected results. That is when there is only a gtk+ interface, no |
84 |
alternative ( ergo, the -gtk is ignored ) and there is a choice between |
85 |
gtk+-1.2 or 2.0 (the gtk2 selection flag) However, this is such a |
86 |
corner case only because the "gtk" flag is completely ignored. |
87 |
|
88 |
|
89 |
//Spider |
90 |
|
91 |
-- |
92 |
begin .signature |
93 |
Tortured users / Laughing in pain |
94 |
See Microsoft KB Article Q265230 for more information. |
95 |
end |