Version: 3.0.90 (CVS) (using KDE Devel) Compiler: gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7) Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --disable-libunwind-exceptions --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux Thread model: posix OS: Linux At bug:83334, I reported a problem with KOffice Part application template. It would be nice if KOffice had an automated (or at least mostly-automated) system to test that all application templates will install, configure, build and ideally run. This would help to prevent regressions. I imagine a DCOP based script that iterates through each template, creating a project that uses that template, running automake & friends / qmake / whatever as appropriate and checking that it builds. The script might need some priming to know what is the correct action for each project, or it might be able to tell from the project file/files.
Even if this didn't work for every template (or there were expected failures), it should at least work for every KDE and KDevelop template.
I find this very interesting and very useful ... especially when we are using some home made project templates for own use.
Wontfix, its insane to expect to install koffice, kdesdk, <your favourite app for which kdevelop has a template> prior to building kdevelop because there are tests in it that provide a koffice plugin. Instead the templates should be properly maintained and it should be made easier to provide user-defined templates. And that is going to happen.