Yep, there is it:
2018-07-04 17:18 GMT+02:00 Nicolai <nicolai-haiku@xxxxxxxxxxxxxxx>:
On Tue, Jul 03, 2018 at 01:28:04PM +0200, miqlas wrote:
There is more than one way to accomplish your goal:
Thank you for the response!
- 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.
This looks very helpful - it's nice to have recipes to follow.
- 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.
This worked for me! The build script now installs the manpages to
/boot/system/non-packaged/documentation/man and I can read them! Now
when I type "man -w" that path is included in the list of directories to
check, whereas before installation, the path wasn't included.
Interesting that Haiku picked it up.