Source: rygel Version: 0.42.5-1 Severity: wishlist valadoc is normally used to build developer-oriented API documentation in an Architecture: all package. It has non-trivial dependencies that are part of a cycle, so we had to disable it during the 64-bit time_t transition, which means rygel has not been recompiled for that transition on armel/armhf until now (although I've just uploaded a version of vala with valadoc restored).
In the case of rygel, the build-dependency is present and the API documentation is built, but I don't see any obvious sign of the API documentation being installed anywhere? It would simplify cross-compiling, builds on new architectures and big transitions like this one if rygel's API documentation was only built during Architecture: all builds (or perhaps even not at all, if it isn't going to be installed), similar to what happens for the gtk-doc or gi-docgen API documentation in GLib and GTK. A full implementation of this would require a trip through NEW to add a -doc package, and would also require something like this in debian/rules (untested): --------------------------------------------------------------------------- built_binaries := $(shell dh_listpackages) configure_options := ... ifneq ($(filter %-doc,$(built_binaries)),) configure_options += -Dapi-docs=true else configure_options += -Dapi-docs=false endif override_dh_auto_configure: dh_auto_configure -- $(configure_options) --------------------------------------------------------------------------- This would also make the build on each architecture quicker. Or, if I'm right about the API documentation not being installed, then the build-dependency on valadoc and the -Dapi-docs=true could just be dropped? Thanks, smcv