jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
<stenur> farkuhar: i have not tried but .. i think having manuals is a major thing. Having them like so is much better than unpacking the ball and looking at the sources.
<stenur> I also asked again last Saturday i think, on #btrfs.
<stenur> Since core commits your things, you could add a generic function to pkgmk or so, which does that stuff, taking a section number as the first argument and a file glob as the second?
<stenur> Ie iterate over the glob and so so.
<stenur> Btw did you say rst? python3-docutils has minimal dependencies and can generate manuals from rst.
<stenur> I use it for one project.
<stenur> (In general most automatic formatters produce _terrible_ UNIX manuals, HTML and PDF are maybe ok, but if you look at the source of manuals ... third class citizens. That is sick!)
<stenur> Ah. I have also removed it.
<farkuhar> stenur: i hope the folks on #btrfs take notice of your request. The documentation in the btrfs source tree uses extensions of RST that python3-docutils cannot handle on its own, hence the test for sphinx in the configure script.
<farkuhar> but unless python3-docutils gets moved to the opt collection, it cannot be a hard dependency of btrfs-progs. Same goes for python3-sphinx, even moreso because of its bigger dependency tree.