On Wed, Aug 19, 2020 at 05:00:24PM +0200, Thorsten Glaser wrote: > > I must admit that I find the trade-off proposed by Adrian and Thorsten > > quite reasonable. I've also looked for more options, but none came to my > > mind. > > I’m actually in favour of one of the other solutions, > not the package split.
I filed a few more ronn-ng bugs (#69, #70, #72); upstream was fairly responsive and they're currently being worked on. I had mentioned #57 previously (that was fixed since), as well as #33 that upstream seems willing to address. These look like they may get fixed in 0.11. However, I went down a different path in the meantime, and worked on packaging lowdown instead: https://kristaps.bsd.lv/lowdown/ (ITP #896816) I had to work with upstream to add some features to make this more viable for both inclusion into Debian, and for this particular use case. With the latest changes that landed in the upstream repository today, generating libmaxminddb's manpages with lowdown should be possible. I also pushed the lowdown package to NEW, so hopefully by the time that reaches the archive, I'll be able to push an even newer upstream that can be used by libmaxminddb. You may be delighted to hear that lowdown is a small codebase, written in C, with only libbsd as an (optional) dependency. Hopefully this will make things a bit more portable for libmaxminddb and possibly other use cases you may have. Finally, I also made a PR against upstream libmaxminddb, that allows one to use translators different than pandoc, starting with lowdown: https://github.com/maxmind/libmaxminddb/pull/248 All in all, this is going to take a little while longer, but is on track to get fixed by having a smaller build-dependency tree. Hopefully this will alleviate any issues you may have had in the past with porting/bootstrapping. Regards, Faidon
