[reposted to opensuse-kde] Hi Stephan, hi *, I'm using the openSUSE KDE packages for quite some time now (but because dependence on some customer installations still on 9.3..), if only it wouldn't break the Qt database bindings more often than not :-(. While I do not understand the rationale behind the "outsourcing" of that stuff packetwise and building it separately, I vote for some build trigger that ensures the rebuild of qt3-extensions in case qt3 is built. These are the current offenders: qt3-3.3.7-29.1 qt3-extensions-3.3.7-30.1 qt3-devel-tools-3.3.7-30.1 qt3-mysql-3.3.7-30.1 qt3-devel-3.3.7-29.1 qt3-sqlite-3.3.7-30.1 qt3-unixODBC-3.3.7-30.1 qt3-postgresql-3.3.7-30.1 Find a minimal test app to list the available database bindings below. Thanks, Pete main.cpp: #include <qapplication.h> #include <qsqldatabase.h> #include <iostream> using namespace std; int main(int argc, char *argv[]) { QApplication app(argc, argv); QStringList list = QSqlDatabase::drivers(); QStringList::Iterator it = list.begin(); cout << "Available Qt database drivers: "; while( it != list.end() ) { cout << *it << " "; ++it; } cout << endl; return 0; } dbtest.pro: SOURCES = main.cpp --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org