| 1 |
On Sat, 23 Jun 2012 18:45:46 +0100 |
| 2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Sat, 23 Jun 2012 19:43:10 +0200 |
| 5 |
> Pacho Ramos <pacho@g.o> wrote: |
| 6 |
> > > It treats -r300 as being newer than -r200, and so will treat "the |
| 7 |
> > > gtk3 version" or "the jruby version" as being newer versions of |
| 8 |
> > > "the gtk2 version" or "the ruby 1.8 version", just as it tries to |
| 9 |
> > > bring in a newer GCC and so on. |
| 10 |
> > |
| 11 |
> > And what problems is that causing for you? |
| 12 |
> |
| 13 |
> The problem is that there's no way of knowing that -r300 is not "a |
| 14 |
> newer version" than -r200 |
| 15 |
|
| 16 |
It is a newer version. That's why it has a newer revision. |
| 17 |
|
| 18 |
> and that the jruby implementation is not "a |
| 19 |
> newer version" than the ruby 1.8 implementation. |
| 20 |
|
| 21 |
And that's another thing which is ugly and should be replaced by |
| 22 |
something sane rather than worked around. |
| 23 |
|
| 24 |
-- |
| 25 |
Best regards, |
| 26 |
Michał Górny |
Archives