There is more than one way to accomplish your goal:
- Packaging that program. It isn't that hard and there is plenty
examples at the https://github.com/haikuports/haikuports repo. You can
just copy-paste parts from existing recipes. With this way you can use
the read-only folders too.
- Building without packagge management: building it just as you did,
but you have to use the non-packaged subfolders, wich are writeable.
Bins should go in /boot/system/non-packaged/bin, while the manpages
should go in /boot/system/non-packaged/documentation/man (however i'm
not sure if man watching this folder or not). You can create folders
in "non-packaged" if they arent exist.
2018-07-03 3:53 GMT+02:00 Nicolai <nicolai-haiku@xxxxxxxxxxxxxxx>:
I'm trying to finalize installation of a 3rd party command-line
DNS/DNSCurve lookup tool called dq. It builds and works as expected, but
I'm not sure where to install the manual pages.
First, I'm installing binaries to /boot/system/non-packaged/bin. Is that
the most appropriate choice?
As for manpages, "man -w" reports a manual page path of
/boot/system/documentation/man, however this directory is read-only.
What's the most appropriate location for 3rd party manpages?
The software in question is: