Re: Using dh for debian-policy packaging
Russ Allbery <rra@debian.org> writes:
> I therefore intend to:
> - Move all the formatting build machinery into the top-level Makefile.
> - Convert the packaging to dh with a minimal debian/rules file.
> - Move the doc-base registration files into debian with *.doc-base names.
> My guess is that nearly no one will care, but if I'm missing some reason
> not to do this, please let me know.
This is now done. I also got rid of a ton of legacy cruft in the build
system left over from previous ways of building the package, and fixed a
bunch of other minor bugs in the process.
XML validation is now applied to the debconf specification and copyright
format (they were previously skipped by being in subdirectories, and the
debconf specification actually failed validation, now fixed). The
publication date for all documents is now derived from debian/changelog,
so should be more reproducible. And debhelper is now responsible for
doing all the gzip compression and getting the flags correct for build
reproducibility.
There's still a bit of irritating duplication of build rules between the
top-level Makefile and the docbook.mk include file that I didn't
eliminate. I'm not a fan of recursive make, so I'm somewhat inclined to
fix this by just getting rid of the nested Makefiles and building
everything from the top level.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: