Hi, some problems with "stable" jabber-server-n-r1: - config-x.tar.bz2 doesn't exist - dodir/usr/jabber-x won't work After fixing both, the ebuild has installed tons of source and objects. I haven't searched for the next error and tried the "unstable" jabber-server -r1 which installed smoothly. Regards, Alkexander
PS: I agree that removing users and groups in postrm isn't fine. There exists an bug for that, I just want to say that too. ;)
As I'm currently trying to figure out how to configure jabber (using the docs from jabber.org) I've stumbled over the fact, that -r2 installs and enables a lot of the gateways like aim, msn etc. I would prefer to install them disabled (as the docs are saying). I would prefer it too, if the jabber.xml from the distribution would be installed, as this file contains a lot of usefull comments for the first-time jabber-admin.
Ok, to use the original jabber.xml with the gentoo installation of -r2, here is a sed. With that and a slightly changed /etc/init.d/jabber which uses a configuration in /etc/conf.d (with comments what those *.xml's in /etc/jabber are providing, the ebuild would be (imho) much better. sed -e 's:./jsm/:/usr/lib/jabber/:' -e 's:./xdb_file/:/usr/lib/jabber/:' -e 's:./spool:/var/spool/jabber:' -e 's:./pthsock/:/usr/lib/jabber/:' -e 's:./dnsrv/:/usr/lib/jabber/:' -e 's:./dialback/:/usr/lib/jabber/:' -e 's:./jabber.pid:/var/run/jabber.pid:' -e 's:<update>:<!-- <update>:' -e 's:</update>:</update> -->:' < jabber.xml > jabber2.xml Regards, Alexander
Euhm, instead of sedding, could you please put them in a tarball, so i can get a closer look? I know the r1 is b0rked, but i really want the r2 to be really stable before releasing it to stable.. I install with the most-used transports since it's so easy to disable them, just comment the line in /etc/init.d/jabber... Other suggestions are welcome, but i'm really leaving the transports inthere.. Thanks
Closing this bug, since r2 is in stable now..
