severity 956041 wishlist thanks On Tue, Apr 07, 2020 at 05:06:02PM +0200, Thorsten Glaser wrote: > On Mon, 6 Apr 2020, Thorsten Glaser wrote: > > > Please do ensure to only ever Build-Depends-Indep on pandoc > > and that the build really only needs it for the arch:all build. > > Erk. The manpages are built like that upstream, so splitting > them into a separate package is required, which… is irksome.
Indeed, creating a separate package for two manpages is indeed a not a great investment of time and resources -- not to mention a policy violation¹ :) > However: > > > This is now very critical, because bind9 recently gained a B-D > > on libmaxminddb ☹ > > I’ve got another idea. Would you be willing to accept a > Debian-specific (but upstreamable) patch to generate the > manpages with a shell script I’d write? This looks to be > doable easy enough, given it’s just the two files in doc/ > and that the -mdoc macropackage supports the semantic > markup used already. I'd prefer to not have to carry a Debian-specific patch that changes the build system for upstream's documentation. Implementing a simple Markdown parser for the few elements the docs have right now (sections and URLs mostly) in shell seems within reach, but it would be error-prone with regards to any future modifications of those documents. Breakages would likely slip through and I wouldn't even notice until a bug report came in. That said, if the patch is upstreamable, I'd encourage you to submit it directly to upstream². Assuming it gets merged in some way or form, I wouldn't mind backporting it before upstream tagged a release. Thanks, Faidon 1: §12.1 "Each program, utility, and function should have an associated manual page included in the **same** package" (emphasis mine) 2: https://github.com/maxmind/libmaxminddb
