to fix stable version that got broken after its stabling. So I revbumped
the stable, fixed it without any other changes, and commited it straight
to stable. And also revbumped the unstable osgi version, so it's still
the newest. Just forgot about updating dep in eclipse, sorry.
OK, I still think it would be better in such cases to avoid having both a stable and an unstable osgi version. Just put the osgi packaging in the stable version - should not cause many problems at this point.
> thus Eclipse is
> currently unusable (as it depends on >=commons-logging-1.1-r4)
Just for users mixing arch and ~arch, though, which is the least
recommended and supported scenario :)
It was unstable for users running arch but who unmasked Eclipse, which is a likely scenario (I myself run arch but for certain packages not yet in stable, unmask them)
I did already.
Thanks, I will also change the JDK requirement to >=1.5 from 1.5 as I've had reports of success building on 1.6 (without changing anything in the ebuild)