On Mon, Apr 07, 2008 at 09:54:34PM +0200, viq wrote: > OK, I finally feel I can show this to people. I'm still not quite sure > it's "perfect", but I can't think at the moment of anything else to > change, and I'm running with it for a couple of days now. > > Certainly my changes to ejabberctl need review, seeing I am doing some > heavy modifications to it (which $UPSTREAM got interested in). Please > have a look at it, whether I do things in a sane way, in proper order, > and so on. > > README.OpenBSD included with some quick tips how to get this running. > > Another thing I'm not sure how I feel about, I tried to keep the way > $UPSTREAM wants it, ie database files now go to /var/db/ejabberd/$NODE/ > instead of old /var/db/ejabberd/ (where unless you modify things NODE = > ejabberd). The steps described in README.OpenBSD for migrating the > databse are certainly the safe way to do things, but since both the old > and the new one keep the erlang node name as [EMAIL PROTECTED] -s` I > was able to just copy my old files into the new dir and run that way. > > SSL is enabled by default in the sample config file. > > During build there's a warning displayed that erlang R12 (what we have > in our tree) is discouraged, but I didn't have any problems with it yet, > and $UPSTREAM says 2.0.1 will have better support for R12. > > Apply with patch -E, our own ejabberd is deprecated in favour of > ejabberdctl, and ejabberdctl is now provided with the distribution > (though rather heavily patched by me)
Lightly tested on amd64, with the README instructions, but without SSL. Looks good so far, registered a User, added some people and chatted. -- simon
