Many net-im, jabber related, ebuilds will be changed to reflect new directory schema introduced by net-im/jabber-base. This is meta bug to track affected ebuilds before they find its way (as revisions) to the portage tree. Ssl
Nice idea. Ok i'm working on jabberd-1.4.4 as there was a big change in the package it will take some time to make a good ebuild and jabber-base compliance.
Ejabberd should comply to jabber-base structure. I do not know if it does, but work has to be done in that direction.
Discussions on the ejabberd site seems to indicate that ejabberd has to be run by a user that has a home directory. Is it possible to work around that in the ejabberd package? Quick search finds http://ejabberd.jabber.ru/node/241 but I can't tell if it is relevant because I have a bad cold and everything is confusing me.
I installed latest jabberd and there's a /var/jabberd/ tree afterwards. But all sample configs want to use (IMHO the more correct location) /var/lib/jabberd/, though the init-script itself uses /var/jabberd/. very strange. Bug? Feature? Confusion? ;-)
Nothing going on here.