jabberd2-2.2.0-r1.ebuild requires choosing a storage backend from {berkdb, postgres, mysql, sqlite} and an auth/reg backend from {berkdb, mysql, postgres, pam, ldap}. This leaves out {oracle, fs} for storage and {oracle, anon, pipe} for auth/reg. "pipe" is a local USE flag. I suggest either: 1. Enable the backends without external dependencies (fs, anon, pipe). Remove the backend checks and the "pipe" flag. 2. Have USE flags for all backends.
Created attachment 158799 [details, diff] implementation of comment 1 option 1 This patch also reorders DEPEND and removes obsolete references to the resolver component.
Created attachment 158801 [details, diff] remove pipe from use.local.desc
Thomas, yes, I agree with you now about the pipe USE flag...I didn't read configure.ac closely enough I guess. I'm favoring option 1 at the moment....Though I think I'd have to revision bump again though, which I'm trying to avoid at the moment.
I think most people using unstable ebuilds understand they'll be bumped more often. Also, the sooner you do it, fewer people will have installed r1 or even 2.2.0. Sometimes, ebuilds are updated without changing the revision, but I don't know the policy about that.
This will make the decision easier: r1 is missing a backslash in econf, disabling every backend except db.
Created attachment 158821 [details, diff] re-enable backends
Ok, I'm going with option 1...but I certainly can't get to this at least until tomorrow afternoon/night
Comment on attachment 158821 [details, diff] re-enable backends Sorry, I should've opened a separate bug. The problem in comment 0 comes with a clear error message and is easy to work around. The problem in comment 5 doesn't and isn't.
Created bug 229957
Ok, Fixed in CVS. Thanks for the report, it's appreciated.
