User manual: expand pathnames based on configure parameters

[clepple]

http://article.gmane.org/gmane.comp.monitoring.nut.user/8680 items 1 and 2

[aquette]

Right, this is one of the last long-run-issue, where I had no simple solution.

Current situation:

• all paths are expressed hard-coded using the default /usr/local/ups prefix
• we already have a big NOTE at the beginning of INSTALL.nut:
  https://github.com/networkupstools/nut/blob/master/INSTALL.nut#L23
  which is turned into HTML:
  http://www.networkupstools.org/docs/user-manual.chunked/ar01s05.html
• we have nothing in the Configuration chapter,
• most of all, nothing at the most suitable place (the occurrences)
• the useful plain text files are not optimized for direct distribution, due to the various asciidoc macros and optimization (comments, anchors, ...). I'm considering, since the beginning, the plain text file generation of Asciidoc, again limited to the useful files.

Early ideas:
I was thinking about spawning a '.in' for each files that includes some paths, and using AC vars (@CONFPATH@ and friends). That's suitable when reading the local docs (i.e. on the computer), but still unsuitable when reading the one from the NUT website

I propose to:

• apply the '.in' files creation
• make an Appendix (separate file), containing the note on path, and listing the various installation paths used on distro
• make a 'path' macro, and replace all existing path occurrences
• generate the "useful plain text files"

There are still point that remains unclear, such as the list of "useful plain text file', if we should add a 'docs/src' to cleanup the distributed source files, ...

[zykh]

We could create a separate .in file filled with AsciiDoc attributes (defaults overwritten with the ones set at configure-time always but when requested to do differently, e.g. for the website; these defaults would work also as fallback values when at configure-time some paths/settings are not given, e.g. --without-udev-dir) and include it wherever we need them:

• https://github.com/zykh/nut/tree/paths-settings
• https://github.com/zykh/nut-website/tree/paths-settings

[clepple]

I changed the title of the issue because we already have a statement in INSTALL.nut that paths will be different for distributions. We should still revisit the AsciiDoc attributes at some point.

[clepple]

Related to #401 ?

[aquette]

Indeed related to #401 @clepple.
The solution is in-between @zykh asciidoc attributes and some generic statements on the paths that are different across the various OS, already existing but not fully applied everywhere, as per #401 ...