| 1 |
Sorry. It's not like I removed them on purpose. This was a special case |
| 2 |
|
| 3 |
> to fix stable version that got broken after its stabling. So I revbumped |
| 4 |
> the stable, fixed it without any other changes, and commited it straight |
| 5 |
> to stable. And also revbumped the unstable osgi version, so it's still |
| 6 |
> the newest. Just forgot about updating dep in eclipse, sorry. |
| 7 |
|
| 8 |
|
| 9 |
OK, I still think it would be better in such cases to avoid having both a |
| 10 |
stable and an unstable osgi version. Just put the osgi packaging in the |
| 11 |
stable version - should not cause many problems at this point. |
| 12 |
|
| 13 |
> thus Eclipse is |
| 14 |
> > currently unusable (as it depends on >=commons-logging-1.1-r4) |
| 15 |
> |
| 16 |
> Just for users mixing arch and ~arch, though, which is the least |
| 17 |
> recommended and supported scenario :) |
| 18 |
|
| 19 |
|
| 20 |
It was unstable for users running arch but who unmasked Eclipse, which is a |
| 21 |
likely scenario (I myself run arch but for certain packages not yet in |
| 22 |
stable, unmask them) |
| 23 |
|
| 24 |
> |
| 25 |
> > Referenced bug is http://bugs.gentoo.org/show_bug.cgi?id=209087, I will |
| 26 |
> > change the Eclipse ebuild to depend on commons-logging-1.1-r6 to fix it. |
| 27 |
> |
| 28 |
> I did already. |
| 29 |
|
| 30 |
|
| 31 |
Thanks, I will also change the JDK requirement to >=1.5 from 1.5 as I've had |
| 32 |
reports of success building on 1.6 (without changing anything in the ebuild) |
| 33 |
|
| 34 |
|
| 35 |
Elvanor |
Archives