-
-
Notifications
You must be signed in to change notification settings - Fork 424
Building and packaging NUT on a system without man page generation tools #3314
Copy link
Copy link
Open
Labels
CIEntries related to continuous integration infrastructure (here CI = tools + scripts + recipes)Entries related to continuous integration infrastructure (here CI = tools + scripts + recipes)Solaris/illumosSolaris and illumos systems (OpenIndiana, OmniOS, SmartOS, TribbliX...)Solaris and illumos systems (OpenIndiana, OmniOS, SmartOS, TribbliX...)documentationimpacts-release-2.8.4Issues reported against NUT release 2.8.4 (maybe vanilla or with minor packaging tweaks)Issues reported against NUT release 2.8.4 (maybe vanilla or with minor packaging tweaks)packagingportabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possible
Milestone
Metadata
Metadata
Assignees
Labels
CIEntries related to continuous integration infrastructure (here CI = tools + scripts + recipes)Entries related to continuous integration infrastructure (here CI = tools + scripts + recipes)Solaris/illumosSolaris and illumos systems (OpenIndiana, OmniOS, SmartOS, TribbliX...)Solaris and illumos systems (OpenIndiana, OmniOS, SmartOS, TribbliX...)documentationimpacts-release-2.8.4Issues reported against NUT release 2.8.4 (maybe vanilla or with minor packaging tweaks)Issues reported against NUT release 2.8.4 (maybe vanilla or with minor packaging tweaks)packagingportabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possible
A troubleshooting session is slowly unrolling at the moment, to build recent NUT for OmniOS (so long as #1498 remains unsolved directly).
There is a neat
make packagerecipe in NUT, which supports legacy SVR4 tooling to make a monolithic package from whatever was built. This relied ondistgoal however, which needs to store pre-built docs, and that failed out of the box.packageit is in fact not really a needed prerequisite, except for AIX RPM (which calls$(MAKE) distexplicitlyStill, a loose thread in the world to pull...
One trouble that remained unresolved is that the
asciidoctoolkit provided there can not in fact build man pages (or I did not pick the right set of dependency packages to make it happen). HTMLs are built, and there was a manual installation of docbook-xml with registration via xmlcatalog to let PFDs happen. So some things work but not everything yet, at least on my testbeds.ooce/text/docbook-xslis installed but files the issue references are not on the system (nor in thatpkg contents)cpin the beginning) with https://mirrors.omnios.org/docbook/docbook-xml-4.5.zipSo the next idea was to use the "dist archive" instead of a build from git, as the recently added GHA jobs produce them nicely. Hard to find, led to adding a https://github.com/networkupstools/nut/wiki/Finding-recent-development-iteration-artifacts wiki page.
It seems the
configure --with-docs=dist-automay have to be used to ship the man pages from tarball instead of locally built ones.--with-docs-man-section-apietc. default section numbers should be neutered if shipping files from tarballs (keep their extensions, even if wrong for the target distro; perhaps warn about that).