| 1 |
On 07/08/2011 06:19 PM, Alan McKinnon wrote: |
| 2 |
> On Friday 08 July 2011 09:14:36 Albert Hopkins did opine thusly: |
| 3 |
>> On Friday, July 8 at 13:11 (+0100), Stroller said: |
| 4 |
>>> Taking a look at this bug today, is there any reason why the |
| 5 |
>>> ebuild shouldn't simply RDEPEND="x11-libs/gtk+" (i.e. remove |
| 6 |
>>> the explicit dep on gtk3), detect what version you have |
| 7 |
>>> installed on your system and then either run --enable-gtk3 or |
| 8 |
>>> --enable-gtk2 during src_configure(), depending upon which |
| 9 |
>>> you're using? |
| 10 |
>> |
| 11 |
>> ebuilds generally don't do this, because it is bad. What you have |
| 12 |
>> and what you want aren't necessarily the same thing. Consider: |
| 13 |
>> |
| 14 |
>> * You don't yet have any gtk installed |
| 15 |
>> * You have gtk2 but actually *want* the gtk3 version, so you |
| 16 |
>> want the ebuild to pull in gtk3 (or vice versa) |
| 17 |
>> * You have both gtk2 and gtk3 installed. |
| 18 |
>> * You have gtk installed, but don't want gtk support for a |
| 19 |
>> particular package (if gtk support is optional for that |
| 20 |
>> package). |
| 21 |
> |
| 22 |
> easy. |
| 23 |
> |
| 24 |
> Two USE flags: gtk2 and gtk3 |
| 25 |
> |
| 26 |
> in ebuild: |
| 27 |
> |
| 28 |
> DEPEND=" |
| 29 |
> gtk2? (x11-libs/gtk+:2) |
| 30 |
> gtk3? (x11-libs/gtk+:3) |
| 31 |
> " |
| 32 |
|
| 33 |
Actually, it's better to have "gtk2" and "gtk". *Not* "gtk3". That |
| 34 |
would repeat the problems of the past (gtk1->gtk2.) |
| 35 |
|
| 36 |
But the devs have gone into ego-mode by now, so there's no chance in |
| 37 |
hell they would accept help or suggestions about this. It has reached |
| 38 |
the point where accepting a suggestion would mean "losing the argument" |
| 39 |
to them, so I doubt they'll do any of it as they don't want to "lose" to |
| 40 |
some n00b users. |
Archives