Especially considering how Gentoo has opted to use seperate config files and processes for the transports and jabberd, the different parts of the jabber server (jabberd, the transports, etc) should be distributed as different ebuilds possibly linked by a meta package. This is often done in other ebuilds and makes sense from the POV of user choice and upgradability of individual programs. Reproducible: Always Steps to Reproduce: Emerge jabber-server Actual Results: I get jabberd, ICQ transport, AIM transport, etc, with the init script configured to try to start them all. Expected Results: I should get only jabberd with init configured to start only jabberd, and installing, for example, the im transport ebuild should then add that and reconfigure the init script.
The transports are still in multiple.xml as well as the seperate xml files. There is currently no simple way to dynamicly make a xml file from a jabber.d directory, so this is currently not implementable. Perhaps later if a xml-building .d script exists.
I accept that answer, but IMO even a post merge message saying "add the following config block to your multiple.xml" file would be better than forcing everyone to install of the transports and upgrade them all to update a single one. But perhaps gentoo as a distribution is trying to get away from such things. I know many programs used to use such instructions but have now gone towards the jabber.d type of configuration instead.
You do not need to install all of the transports. The latest ~x86 ebuild has local USE flags to disable them. Try: emerge -vp jabber-server
