| 1 |
El sáb, 23-06-2012 a las 18:45 +0100, Ciaran McCreesh escribió: |
| 2 |
> On Sat, 23 Jun 2012 19:43:10 +0200 |
| 3 |
> Pacho Ramos <pacho@g.o> wrote: |
| 4 |
> > > It treats -r300 as being newer than -r200, and so will treat "the |
| 5 |
> > > gtk3 version" or "the jruby version" as being newer versions of |
| 6 |
> > > "the gtk2 version" or "the ruby 1.8 version", just as it tries to |
| 7 |
> > > bring in a newer GCC and so on. |
| 8 |
> > |
| 9 |
> > And what problems is that causing for you? |
| 10 |
> |
| 11 |
> The problem is that there's no way of knowing that -r300 is not "a |
| 12 |
> newer version" than -r200, and that the jruby implementation is not "a |
| 13 |
> newer version" than the ruby 1.8 implementation. |
| 14 |
> |
| 15 |
|
| 16 |
Regarding -r300 issue (I don't know much about ruby), I guess paludis |
| 17 |
wants to install net-libs/webkit-gtk-1.8.1-r301 for example when nothing |
| 18 |
is requiring any specific SLOT? What problems does it cause apart of |
| 19 |
what would cause if ebuilds using gtk2 are RDEPENDing on plain |
| 20 |
x11-libs/gtk+ without specifying any SLOT? In both cases gtk2 apps |
| 21 |
should RDEPEND specifically in SLOTs for gtk2 support and gtk3 apps on |
| 22 |
gtk3 slots. |
Archives