I've been looking around for bad dependencies on my system and see that the most recent versions of gob make it one of only two or three apps which explicitly depend on glib-2.0*, rather than >=glib-2.0.0 It compiles fine with glib-2.1 (which is not in portage), and the most recent ebuild should likely be changed to reflect this. Furthermore, gob-1.99 and up have been masked since July with a note stating that the dependencies on 1.x needed to be corrected. Only gnome-pilot and evolution depend on 1.x (both with >=), and both compile fine with 2.0... Given this result, later versions of gob need not install into a seperate slot. Thus, I believe that gob can also be safely unmasked. (Note, however, that I tested evolution-1.2 and not 1.0.8) For future reference, should similar reports be under component 'Ebuilds', or is this fine?
this is fine, it is a bug in the current tree not an enhancement... i will look at it soon
Are you sure you just didnt have both around (i really think you had) ? Anyway, i fixed the gnome-pilot and evolution deps and removed gob2 from package.mask . Thanks for your report
Did I have both of what around? gob? I used a custom ebuilds which used the same slot when I was testing that stuff, so emerge clean should've gotten rid of all traces of the older version. Not that the SLOT stuff is that important, though.
