Hi, I have successfuly emerged net-im/jabberd on my g/fbsd and it's running fine. However, i had to modify the ebuild in order to get it to compile with the right sys-libs/db and not the fbsd's /usr/include/db.h. See the diff attached below. So it can be keyworded for ~x86-fbsd, and don't forget net-im/jabber-base too. Thanks.
Created attachment 113521 [details, diff] diff from the original ebuild
Maintainer: please apply this patch, and reassign back to BSD once that's done, so that we can keyword. Also, sys-libs/pam dependency might need to be changed to virtual/pam, in case I'll look into it and report here tonight (hopefully), or mask the flag if it's depending on sys-libs/pam proper.
Is the db issue a problem for jabberd-2.1.6 or just jabberd-2.0.11? I assume that both versions are affected. The jabberd-2 documentation states, that pam support is for linux only.
That would be quite strange, it might be Linux-PAM only (which is not the same as being for Linux only, Linux-PAM was used by FreeBSD 4.x, and currently by Mac OS X), and that would be acceptable, but Linux-only sounds heavily suspicious. Anyway I'll see to look at it now; I was planning to work on the transition-overlay but I forgot the URL :(
Sorry if my comment was misleading: It is linux-pam only. No openpam support.
I'd like to deprecate jabberd-2.0* in favor of jabberd-2.1*, so the 2.0 series is not an issue.
I'm currently building against OpenPAM, a quick check over the sources finds no reason to think it won't work (note that PAM API is standardised, and the only reason there is to not work with OpenPAM is if Linux-PAM's own extensions are used; and even in that case it's usually easy to rewrite the code not to sue them). The other reason could be only using modules like pam_limits.so that is available only on Linux, but that does not seem the case for jabberd. And yes, I'm testing 2.1 not 2.0.
D'oh! The init script will not work with baselayout 2, as it's not POSIX-compatible. Will try to fix it too.
Okay I have a patch for the init script that I'll now attach. The pam dependency should be fine changed to virtual/pam I think, but I wonder, did anybody try the pam support before? I ask because it needs a pamd file that is _not_ installed, and even if I create it, it seems to be trying the username "flame@prakesh.flameeyes.is-a-geek.org" to authenticate, and that's not a valid username as far as I remember, for any version of PAM (@), plus is too long on FreeBSD anyway.
Created attachment 121951 [details, diff] Patch for jabberd init script Here it comes, with that patch the init script works on FreeBSD. This and the patch to the ebuild, and jabberd can be safely keyworded ~x86-fbsd.
Thanks for testing/fixing stuff. Did you still need the db fix to be able to compile with correct sys-libs/db? The pam behavior is "normal" at the moment, upstream is working on a fix (http://jabberd2.xiaoka.com/ticket/17).
Shouldn't the PAM support be disabled then, rather than given an useflag, at least till upstream fixes it? When they do, it would also require a proper jabberd pam.d file (or it won't authenticate; myself I've been using the same as imap from mailbase -- make sure you don't use pam_stack if you provide a custom one). And yes, I still need the db fix or it finds the libc's db.h file (which is for db 1.85). There's also another problem with db versions, but that's not jabberd2-specific, so you don't have to mind about it :)
Seems net-im/jabberd is not relevant to sys-libs/db and virtual/pam. I've added ~x86-fbsd to it. Now I'll take a look at net-im/jabberd2
Added ~x86-fbsd also to jabberd2. Closing.
