I got into this when looking for old packages requiring the dead gnet lib. Then I saw that also Debian killed it because of this bug:
Maybe we could also treeclean it :/ I have also failed to reach upstream homepage
this is also the only consumer of net-libs/gsnmp
What is actually wrong with net-libs/gnet?
It is a bit explained by upstream at:
(In reply to Pacho Ramos from comment #3)
> It is a bit explained by upstream at:
That's a couple of pages of text none of which seems to relate to the question I asked: What is actually wrong with the library?
Does gnome@ intend to remove net-libs/gnet? Are other packages affected besides the ones you mention here? Is there any urgency in removing net-libs/gnet, like security issues?
There is no known urgency to me, but gnet development stopped at 2008 and no-one does any kind of security audits or whatever on it. Sooner or later it is prudent to remove stuff not maintained upstream for 10 years. Rather sooner than later. Additionally if things still rely on that, instead of much better glib GIO networking layer (available for half a decade or more), then that points to unmaintained upstream of these consumers as well.
So to summarize:
gsnmp: last ebuild update Nov 2014 (adding local patches), last (and only) version added in Jun 2011
scli: last ebuild update Nov 2014 (adding local patches), last bump in Sep 2012
Both packages are ancient, have no upstream and (given no bug reports in Gentoo) likely aren't used by anyone. With no homepage and being removed from most of the other distributions, it's quite likely that they have no more than a few users. In the end, we can quite positively assume they may have security bugs nobody noticed.
So, do you have any actual argument for keeping those packages?