!!! Multiple versions within a single package slot have been !!! pulled into the dependency graph: dev-libs/libsigc++:2 ('installed', '/', 'dev-libs/libsigc++-2.0.18', 'nomerge') pulled in by ('installed', '/', 'net-irc/lostirc-0.4.6-r1', 'nomerge') ('ebuild', '/', 'dev-libs/libsigc++-2.2.2', 'merge') pulled in by ('installed', '/', 'dev-cpp/glibmm-2.16.0', 'nomerge') ('ebuild', '/', 'media-gfx/inkscape-0.46-r1', 'merge') ('installed', '/', 'dev-cpp/gtkmm-2.12.5', 'nomerge') The dependency on =dev-libs/libsigc++-2.0* seems to be present in lostirc since 0.4.0, as indicated by the URL above. I would assume that current versions should cooperate with current libsigc++, and that the dependency can be generalized to >=dev-libs/libsigc++-2.0. I just tried a version compiled against libsigc++-2.2.2; it compiles, runs and I can even chat on #gentoo, so I'd assume that combination works. If there is a really good reason why lostirc won't cooperate with libsigc++-2.2*, then maybe an additional slot can be used for this. Although this can't be done by simply changing the SLOT of one of the ebuilds, as they both install libsigc-2.0.so.0.0.0. So i hope there is no real reason to keep libsigc++-2.0* around while programs depend on 2.2*.
The Changelog doesn't indicate anything... Also cc'ing gnome-mm for possible 2.2 slot.
Nope, 2.2 is still in the same SLOT="2" like 2.0.18. So no slotting needed. For info, 2.2 removes the old API/ABIs that were deprecated in 2.0. I guess lostirc's dep can be modified to just >=libsigc++-2
Ping?
lostirc has bigger issues, eautoreconf doesn't even work...
net-irc/lostirc was removed from portage.
