1 |
I have a question regarding the gtk/gtk2 use flags - I recall a |
2 |
discussion recently that, if memory serves, basically said "gtk2 should |
3 |
be completely ignored if -gtk is present." |
4 |
|
5 |
Did I misinterpret this? Shouldn't USE="-gtk gtk2" be acceptable? It |
6 |
seems to me that "gtk" is used to say "I want gtk support when it is |
7 |
optional" and "gtk2" means "When both gtk-1 and gtk-2 support is |
8 |
available, use gtk2." So, to this end, "-gtk gtk2" should mean "if a |
9 |
package doesn't require gtk (of any version), don't build it. If it |
10 |
does require gtk, use gtk2 support if possible." |
11 |
|
12 |
Did I misunderstand the previous discussion, or is the above assumption |
13 |
correct? |
14 |
|
15 |
-- Jason Rhinelander |
16 |
-- Gossamer Threads, Inc. |
17 |
|
18 |
|
19 |
Spider wrote: |
20 |
> Okay, |
21 |
> I spoke up a while ago about this, and came with correct and |
22 |
> suggested syntax for theese problems, but there seems to be a LOT of |
23 |
> cruft in the tree anyhow. |
24 |
> |
25 |
> |
26 |
> I did some grep for "gtk2" IUSE statements, and went through them all. |
27 |
> I'm sad to say that the majority of all ebuilds i found have severe |
28 |
> logic flaws. |
29 |
> |
30 |
> Thats correct, Most of the builds -DONT- work either as they should nor |
31 |
> as intended. |
32 |
> |
33 |
> |
34 |
> Here is a list of broken ebuilds ( i tried to just get the latest |
35 |
> version ) , comments on -why- they are broken, and how it should be |
36 |
> done. |
37 |
> |
38 |
> I dont have explicit knowledge about all theese builds, so some may be |
39 |
> special cases, but far from all are. |
40 |
> |
41 |
> |
42 |
> ATTN DEVS! |
43 |
> I want you all who are -responsible- for theese to go through and fix |
44 |
> this. ASAP. |
45 |
> |
46 |
> |
47 |
> I could just as well have gone through all theese myself and checked |
48 |
> in the changes, but noone would learn what they were doing right by me |
49 |
> just fixing things for them. Thats why I want the various maintainers |
50 |
> to have looks at it and fix. This way I hope I will Never have to face |
51 |
> this problem again. |
52 |
> |
53 |
> |
54 |
> If I find more builds with the same logic flaws in the future, I will |
55 |
> hard mask said builds and bug the maintainers in private, but this is a |
56 |
> wide sweep and I grabbed all of those that were on my list, checked and |
57 |
> signed up here. |
58 |
> |
59 |
> If you feel overwhelmed by the stuff you have, I'm sure there are bored |
60 |
> people around who want a go at cleaning things out, Just say so and it |
61 |
> will be fixed, we're a community after all. |
62 |
> |
63 |
> |
64 |
> But, I feel like a grumpy old man now after wading through errors and |
65 |
> bugs (and bugzilla was too slow for me to even be usable, or you would |
66 |
> have had bugs a plenty there too. Hah, saved you were ;) so do take the |
67 |
> time to check the list, see what mistakes others have made, |
68 |
> And Dont Repeat Them. |
69 |
> |
70 |
> |
71 |
> Regards, |
72 |
> Spider |
73 |
> |
74 |
> |
75 |
> |
76 |
> |
77 |
|
78 |
|
79 |
-- |
80 |
gentoo-dev@g.o mailing list |