This ebuild adds the xdb_sql backend to jabberd for using a sql server for the jabber spool. It actually support mysql,pgsql,oracle, and odbc, but it can only support one at a time (defined at build time). Since mysql was the one I needed I have only added support for that. I don't know how we would handle if the user has multiple USE flags defined since we can only use one of them.
Created attachment 28800 [details] jabberd-1.4.3-r3.ebuild ebuild to add xdb_sql support to jabberd
Your ebuild doesn't work. Change this: cd ${S}/xdb_sql/src to cd ${S}/xdb_sql Also, its got some other small errors, nothing else that keeps it from merging properly, though. lintool it.
Created attachment 28916 [details] jabberd-1.4.3-r3.ebuild Fix typo and lintooled
Just an FYI, the ebuild for jabberd-2.0 shows how to use multiple oracle/mysql/postgres use flags ..Just an FYI, the ebuild for jabberd-2.0 shows how to use multiple oracle/mysql/postgres use flags ..
As it is right now this could never make it into portage because as you say this can use any backend sql database but the ebuild only allows mysql, this bust handle all options even if it forces the user to only have one of mysql postgresql in use vars.
I was giving a closer look at this package and i noticed that altough http://www.jabberstudio.org/projects/xdb_sql/project/view.php says that this GNU GPL the COPYING file is empty. I sent a mail to upstream with a request for clarification because of this note in the README file: "This program is Open Source software and is subject to specific conditions of distribution and modification (see the COPYING file)."
I just got confirmation from one of the previous maintainers that this GPL. So just need's the ebuild fixed.
re Comment #4, this is different. jabberd supports having multiple backends compiled in, whereas this specific module wants you to pick only one backend, it can't support multiple. You can have mysql OR pgsql OR oracle OR odbc, but you can't have a mixture of them. I suppose if you had more than one set we could eerror out telling you to choose one, but that seems a bit messy to me. We could assign priorities to them, but then a person expecting to get the lower priority functionality could end up with the higher one instead and not understand why. The other option would be to use an env. variable such as $JABBERD_DB_BACKEND, that could be set at emerge time or in make.conf, but that is just messy. Ideas?
jabberd-1.4.4-r3 has xdb_sql - mysql and postgresl support. Currently masked for further testing. Reports about whenever it works, or no should go to bug #149358
