Alexandre Rostovtsev wrote: > On Mon, 2014-06-23 at 22:15 +0200, Jörg Schaible wrote: >> So, why the heck, was the dependency to dev-libs/glib changed for an >> existing ebuild without increasing its version (e.g. >> dbus-glib-0.100.2-r2)? > > Please see http://article.gmane.org/gmane.linux.gentoo.devel/91615
These blocks had nothing to do with the multilibs ABI. It has been just the updated versions for the dependencies. >> I have to use an older Eclipse 3.8.x version for my daily work and since >> it is broken with latest gtk versions (a lot of crashes), I use still >> some old ebuilds and have masked new ones. > > Please file a bug report about this. If nobody tells us that a new gtk+ > version broke something important, we will soon mark the new version as > stable and then remove the old version. I report anything, if it is worth it. However, in this case the problem is on Eclipse's side and fixed in newer versions. Alas, it does not help me, because I have to use that old version for my daily work. So, there's no blame on Gentoo and nothing the devs should have to waste their time. Therefore I still use the once stable versions of GTK (~5 months old now), where this old version of Eclipse runs, i.e. I already preserved some older versions locally that are already vanished from the portage tree. The newer ones are hard masked. However, if some of my currently installed stable packages suddenly require newer versions, my portage tree gets in serious trouble. Nothing would have happen if the revision number of the affected packages had been simply increased. Cheers, Jörg
