Select build options explicitly and record the resulting configuration summary. For packaging, ./configure --with-all can help expose missing prerequisites and newly available features; disable unsupported features explicitly. --with-all=auto instead selects features whose prerequisites are detected in the build environment, so the resulting package contents can change when that environment changes.

Use the options documented in docs/configure.txt to set installation paths. In particular, --with-confdir controls NUT’s configuration location; options for driver, state, PID, CGI and HTML paths serve different purposes and should match the integration policy for the target distribution. Do not copy a path layout from another platform without checking its conventions.

Stage installation into a packaging directory with DESTDIR, as described in INSTALL.nut.adoc. Keep the configured final paths distinct from this staging prefix. Inspect the staged file inventory and derive package contents and dependencies from the actual build, including shared-library metadata and optional scanner libraries. Do not replace administrator configuration with example files during an upgrade.