Currently, psycopg >= 1.99 is masked because psycopg in that version had a different api than psycopg1 but kept the same package name. However, from psycopg 2 on, the package name was changed to psycopg2, and hence can be installed simultaneously in a different SLOT and doesn't need to be masked. I propose dropping the 1.99 ebuild (no one should use it, it is broken), unmasking and slotting psycopg2, and while you are at it version bumping to 2.0beta8. I'll add an ebuild to this bug shortly.
Actually, the ebuild for 2.0beta5 is already SLOTted, so it just needs a version bump to beta8, no changes necessary.
2.0_beta8 can also be keyworded ~ppc.
Psycopg 2.0_beta8 also runs fine on amd64.
Psycopg2 was officially released 2006/06/08. I'm currently running psycopg2-2.0.2 without any problems (x86). In the event it's helpfull I'll post the ebuild I'm using. Cheers, John M.
Created attachment 89055 [details] Psycopg2 post release ebuild (second poin release) works for me on x86.
before it gets unmasked, we have to go through the tree to change all the deps of packages to <dev-python/psycopg-1.99. dev-python/adodb-py dev-python/django dev-python/orm dev-python/sqlobject net-zope/zpsycopgda www-apps/trac
Created attachment 92742 [details] psycopg-2.0.2.ebuild New ebuild supporting 'debug' USE flag
Created attachment 92743 [details, diff] psycopg-2.0.2-nodebug.patch patch used by psycopg-2.0.2.ebuild
I just added a newer version of the 2.0.2 ebuild which removes the 'PSYCOPG_DEBUG' flag unless the 'debug' USE flag is specified.
thanks dustin, i've now unmasked psycopg-2.0.2 along with modifying all the psycopg deps for packages that do not support both versions.
