| 1 |
I'm not expert enough on this subject to be *advocating* this approach, but this is how I would have expected it to behave: |
| 2 |
|
| 3 |
On 8 July 2011, at 14:14, Albert Hopkins wrote: |
| 4 |
> |
| 5 |
> On Friday, July 8 at 13:11 (+0100), Stroller said: |
| 6 |
> |
| 7 |
>> Taking a look at this bug today, is there any reason why the ebuild |
| 8 |
>> shouldn't simply RDEPEND="x11-libs/gtk+" (i.e. remove the explicit dep |
| 9 |
>> on gtk3), detect what version you have installed on your system and |
| 10 |
>> then either run --enable-gtk3 or --enable-gtk2 during src_configure(), |
| 11 |
>> depending upon which you're using? |
| 12 |
> |
| 13 |
> ebuilds generally don't do this, because it is bad. What you have and |
| 14 |
> what you want aren't necessarily the same thing. Consider: |
| 15 |
> |
| 16 |
> * You don't yet have any gtk installed |
| 17 |
|
| 18 |
Highest version of gtk in tree is pulled in as a dep (subject to masking, ARCH, ~ARCH, &c) |
| 19 |
|
| 20 |
> * You have gtk2 but actually *want* the gtk3 version, so you want |
| 21 |
> the ebuild to pull in gtk3 (or vice versa) |
| 22 |
|
| 23 |
emerge -u1 x11-libs/gtk+ (assuming gtk3 is now stable) |
| 24 |
or |
| 25 |
emerge -1 =x11-libs/gtk+-3.0.10 |
| 26 |
|
| 27 |
(but gtk3 will probably be pulled in by Gnome3 (??) automatically when the user upgrades to that) |
| 28 |
|
| 29 |
> * You have both gtk2 and gtk3 installed. |
| 30 |
|
| 31 |
Compile against the higher one |
| 32 |
|
| 33 |
> * You have gtk installed, but don't want gtk support for a |
| 34 |
> particular package (if gtk support is optional for that |
| 35 |
> package). |
| 36 |
|
| 37 |
This is when you should be using USE="-gtk", surely? Whether v2 &/or v3 of gtk is supported is irrelevant. |
| 38 |
|
| 39 |
Stroller. |
Archives