On Wed, Dec 05, 2018 at 08:33:09AM +0000, Jonathan Dowland wrote:
> I've done so, thank you. The upload should close this bug. But, since
> the cross build failure remains, I think it would be nice to have a bug
> open to track that. I could clone this one for that purpose, but I don't
> know whether you would like the cloned bug to be usertagged (as this one
> is) or not.
You can as well reuse this bug. I've taken note that you've applied my
patch exceptionally quickly, so I don't need the closure of the bug to
retrigger a build anymore.
Let me summarize the options for making the documentation work for
cross:
* Remove documentation from the package. That may sound ridiculous, but
Arch:all packages are irrelevant for cross building, so splitting it
out would fix it. Adding a binary package for a single manual page
seems like a bad trade-off to me though.
* Add a nodoc build profile and say that duc can only be cross built
with nodoc.
* Build duc twice^Wfour times. Another build pass could be added for
the documentation:
ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
dpkg-architecture -a$(DEB_BUILD_ARCH) -f -c dh_auto_configure ...
endif
* Generate the documentation at release time rather than build time.
* Somehow generate the documentation without running duc during build.
* Add "duc:native <cross>" to Build-Depends and build the documentation
from the system copy of duc during cross compilation only.
None of these looks particularly attractive. I'm not sure whether it is
worth the effort. Using dh_auto_configure has advantages in
maintainability beyond just cross building, but this?
Hope this helps
Helmut
