mediawiki (>=1.7.1= can use postgresql as it's database backend. Making the deps depending on USE-flags would be nice. Problem: tsearch2 in postgresql is needed.
I might have a suggestion, would you mind to be the tester of this ? I don't have postgres installed, I don't know about trapni. I should take a look at this now, I have a bit of free time right now.
Here is my suggestion, wait for Mediawiki 1.8 and postgres-8.1 to stabilize. Before that I could make a -r1 for the extra use flag, but I would not like to support this before the mediawiki people say they are happy with it. OR if someone become the postgres mediawiki maintainer / tester. More googling has pointed to some bugs and issues related to <postgress8.1 and mediawiki-1.7.x, IRC comments are also pointing in that direction. This is what mediawiki says: ============================ SQL and MySQL Wikipedia currently uses MySQL as the database backend. Make sure MySQL support is compiled into PHP! We're also trying to make the wiki work with other database backends, particularly PostgreSQL, out of performance and portability concerns. Version 1.7 should have rudimentary support for PostgreSQL.
Did I understand it correctly, that 1.7.x is the mediawiki "development tree"? If yes, I don't think that they'll release it with a broken support of postgresql. And version 1.7.1 of mediawiki it is still '-*' keyworded anyway. Btw: I have mediawiki-1.7.1 with postgresql-8.1.4 running here. The installation has some pitfalls and I had to make some modifications in the mediawiki ebuild to get the postgres sql scripts installed, but it seems to work.
1.7.x is not a development version, but the support for postgres will be matured in 1.8.x. At least that is what I am guessing from the readings of today. Also postgress-8.1 is not yet stable, again because of readings on the subject, I am not willing to make mediawiki support it until postgres-8.1 is stable. Here is one idea, we wait a little longer, mark 1.6.8 stable, mark 1.7.1 ~, wait for postgres to stabilize and have -tsearch2, fix the ebuild for postgres wait 30 days and stable it ?
Sorry, again postgresql-8.1.4 should also fix the -tsearch2 problem. So let's just wait for that, I was planing to stable 1.7.1 end of october if there is no other bugs, that's why I'd like to wait to add postgresql.
There's no problem with tsearch2 in postgresql-8.1.4 (or am I wrong?). We have tsearch2 support in postgresql (>=8.1.4), bug #145758 is more or less obsolete, but we decided to keep it open until I'm able to commit the new ebuilds from the postgresql overlay into the tree and to mark postgresql stable.
noone of our systems is running postgres so far '(
OK we got the 1.8.0 release * Full Postgres support is now enabled. It requires version 8.1 or better, and needs to have both plpgsql and tsearch2 already installed. Could you verify about the plpgsql on the gentoo default setup, or do we need yet another depend ?
I have now commited 1.8.2, I'll close this bug soon if I don't hear from anyone. I will also remove the postgres USE flag as I cannot test this myself, someone has to take the testing of it.
mediawiki-1.8.2 has now support for this, while postgres is not yet market stable it can be tested.
