While trying to get net-im/aim-transport installed for jabberd, I noticed that the ebuilds fo net-im/jabberd-2.x overlap with net-im/jabberd-1.4x. Portage allows both to be installed at the same time, but the /usr/bin/jabberd executable is created for both versions; whichever version is installed last will overwrite the existing one, leaving an unrunnable jabberd server. From the official jabberd docs, it appears that jabberd 1.4 is necessary to run the aim-transport and that the intended configuration is for jabberd 2 to provide the main server and jabberd 1.4 to provide just the transport and hook into jabberd 2. If the two are meant to co-exist, the ebuilds should make this possible.
It seems aim-transport isn't updated any longer. I would recommend pyaim-t which is not in portage yet.
jabberd-1.4.4-r3 doesn't depend on aim-transport anymore (it has a block against aim-transport). aim-transport will be removed after 1.4.4-r3 goes stable. It is currently masked for further testing, bug #149358 will track progress for stabilization of 1.4.4-r3. After it goes stable all <1.4.4-r3 will be removed.
