kdesvn-build 1.6.2

kdesvn-build 1.6.1 had some issues in the sample configuration regarding the build order of phonon and kdesupport so I’ve taken that fix and a few others and have released kdesvn-build 1.6.2. It’s also the first kdesvn-build that I’ve digitally signed. I’ve had a GPG key for awhile now but I’ve not put the effort into signing the code because it didn’t seem necessary. Someday I’ll actually get to go to Akademy and thereby get my key signed but until then at least there’s a bit more trust you can associate with the code.

As far as future directions for kdesvn-build, what I’m working on now is code to allow kdesvn-build to have a persistent data store. This will be initially to support wish 157992, to avoid the bother of running make/make install if no source update occurred. I envision keeping track of the last time a module was successfully built and installed for each module and using that to implement the feature.

But is there any other bit of data that would be useful to retain about modules and what gets built? Note that I’m referring to things that are not easily looked up after the fact. The revision on disk, for instance, is easily queried.

One other kdesvn-build nit is that the program currently will automatically approve the KDE SVN SSL signature for those using https:// since otherwise the program may freeze forever waiting for a user confirmation which the user can’t see (normally output is logged and not sent to tty). I don’t really like the idea of doing that but the alternatives are to have the user cache the authorization for the KDE SSL server instead of kdesvn-build or to configure Subversion not to prompt for KDE’s SSL certificate (either by local configuration or by KDE somehow obtaining a cert that OpenSSL can trust by default). Either way is work I’d rather avoid putting the user through. Thoughts/suggestions are appreciated.

One last thing, kdesvn-build will require at least Perl 5.8 in the future (and may already as I have no 5.6 to test against). In addition if anyone wants to look at the documentation and give me recommendations for improvement (or better yet, patches ;) I’d appreciate it.