As for the man page (re)builds, there might be a better way to handle that, but de-facto there are two sets of target lists in docs/man/Makefile.am: * man5_MANS (more for other numbers, other formats) that would build just the pages needed for your drivers, developer features etc. requested by configure script * MAN_MANS and HTML_MANS that would build (and are used to check) all docs there are for a format, regardless of whether you build a driver or daemon for it today.
Of these, MAN_MANS are (usually) pre-built and dist'ed in the tarball, so a build system is not required to have asciidoc to package NUT, and can use pages from the tarball "as is". But fair point, I'll add a `make all-man` in PR #1345 spawned to tune builds to cover netbsd better :) On Wed, Mar 30, 2022, 19:02 Greg Troxel <[email protected]> wrote: > > * make check > > When I run make check, the good news is that it seems to pass > everything. > > But it looks like it is building man pages that maybe should have been > built during the build. > > [snip] > Making check in docs > Making check in man > make check-local > PASSED man-source sanity check (checked 130 files) > DOC-MAN Generating hosts.conf.5 > DOC-MAN Generating upsset.conf.5 > DOC-MAN Generating upsstats.html.5 > DOC-MAN Generating upsset.cgi.8 > [snip] > > * make install > > looks good > > * make distcheck > > This fails because of missing libneon, but the earlier configure worked. > Is the configure intentionally forcing on all optional things? > > _______________________________________________ > Nut-upsdev mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev >
_______________________________________________ Nut-upsdev mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
