I dropped your keywords from tkabber 0.11.0 because there are two new dependencies that are not tested on your architectures: dev-tcltk/tktray dev-tcltk/tkimg
# emerge -av tkabber These are the packages that would be merged, in order: Calculating dependencies - emerge: there are no ebuilds to satisfy ">=dev-tcltk/tktray-1.1". (dependency required by "net-im/tkabber-0.11.0" [ebuild]) # eix tktray No matches found. Nice. And they're not even dependencies anyway - http://tkabber.jabber.ru/files/doc/tkabber.html#s.requirements
oops, tktray has not been committed.. forgot to hit commit.. I know its not an absolute depenency, but really, its a major feature and it only brings in a small package, so I have no plans to make it an optional dep. If your architectures want to skip tkabber entirely, I'm fine with that.
Keyworded tktray, tkimg and tkabber on alpha. Note that tktray needs a valid X11 connection for tests; for most people, it won't work, so it might need a fix. Testing "by hand" works ok, though. Also, I think that tkimg's metric asston of repeated eautoreconf and configure runs isn't the most effective approach. It took several orders of magnitude (sic) longer to configure than actually compile.
all 3 are ~sparc now, closing since we're last