PR1.2 SDK and the Extras autobuilder
Niels Breet has, in this month's maemo.org sprint, picked up a task to sort out the issues caused by the deployment of the PR1.2 SDK to the Extras autobuilder. This has resulted in new uploads from developers often getting dependencies more severe than they actually require, and users who are testing in Extras-devel and Extras-testing getting confused. Andrew Flegg, the Maemo Community Council chair, introduced a discussion on maemo-developers, saying, After the PR1.2 SDK was released, Niels deployed it to the autobuilder; enacting a plan which was discussed on this list. This has caused problems with libhildon dependencies, but the problems aren't just limited to that library. Both Niels and the Council believe we should do something to assist. Although "real" end-users (who use Extras) are unaffected, anyone with an idea on how to meet the requirements now - and the next time this situation could occur - is welcome to contribute. The current leading option is one based on a deploying a newer debhelper and dpkg-shlibdeps to the autobuilder. This would mean that every package would have its minimal dependencies necessary for it to work.