Guys,

  Just an update. I was able to get applications/kde-style-qtcurve to build with
the existing CMakeLists.txt, but as with gtk-qt-engine, it doesn't look like a
normal Trinity cmake file. This brings the current Trinity packages building on
Arch to:

trinity-app-amarok-1222475-1-x86_64.pkg.tar.xz
trinity-app-gtk-qt-engine-1222892-1.0-x86_64.pkg.tar.xz
trinity-app-style-qtcurve-1182805-1-x86_64.pkg.tar.xz
trinity-arts-1214641-1-x86_64.pkg.tar.xz
trinity-kdebase-1222475-1-x86_64.pkg.tar.xz
trinity-kdelibs-1222475-1-x86_64.pkg.tar.xz
trinity-kdevelop-1222477-1-x86_64.pkg.tar.xz
trinity-kdewebdev-1222551-1-x86_64.pkg.tar.xz
trinity-pyqt3-3.18.1-9-x86_64.pkg.tar.xz
trinity-qt3-3.3.8-20-x86_64.pkg.tar.xz
trinity-tqtinterface-1222551-1-x86_64.pkg.tar.xz

  Let me know if there are additional modules that should build under cmake. I
have been watching svn update and browsing through the applications directory to
see what might build. We should keep a list of what is currently ported and
should be working. That way we can concentrate building on the new packages to
catch build errors.

  If I can get my hands on a complete list, I'll add it to the HowToBuild wiki
page so we have a running list.

  Also, if we should not expect the apps with the older generic looking
CMakeLists.txt to work properly, let me know and I'll hold off making the
development packages available to Arch. Thanks.

-- 
David C. Rankin, J.D.,P.E.