$subject
*** Bug 220967 has been marked as a duplicate of this bug. ***
Any chance of getting the actual release into portage, even if it is still masked? I tried simply copying the rc ebuilds into a local overlay and renaming them, but couldnt get qt-sql to compile without adding additional target dirs.
Yes, I'm working on that. I'm not committing Qt-4.4.0 without sufficient testing. And bumping vs committing are entirely unrelated, unmasking depends on tree-wide dependencies on x11-libs/qt:4 being fixed.
On topic of qt-sql: it has an unneeded dependency. dev-db/postgresql is in no way needed to build qt-sql with postgres useflag. Only a simple fix is needed: adding `sed -i -e '/pg_config --libs/d' "${S}"/configure` to src_unpack.
Hey, the ebuild that got today into the tree (one depending on the virtual) is broken. It still needs that sed line. It's due to the fact that `pg_config --libs` prints: -lpgport -lpam -lssl -lcrypto -lkrb5 -lcom_err -lz -lreadline -lcrypt -ldl -lm and pgport is neither installed by libpq ebuild nor needed by qt-sql. Please, add this line.
Anything new about qt-sql ? I restate: if you have only libpq installed (no dev-db/postgresql), then x11-libs/qt-sql with useflag postgres will simply fail to build without that sed line.
I've emerge QT 4.4 yesterday on Portage 2.1.5.2 (default-linux/amd64/2007.0, gcc-4.2.4, glibc-2.7-r1, 2.6.25-gentoo-r4 x86_64) and it works. QT-webkit also (tested by compiling and using arora). PyQt4.4 also builds against QT 4.4 and works nicely.
Is my comment being ignored for some reason or is just ignored ?
I've commmitted 4.4.1 and unmasked that version only. qt-sql now depends on virtual/postgresql-base, so that is addressed as well. Enjoy!
