Manpage references `main.exe.conf`

[ydirson]

Apparently the build produces a main.exe binary which will later be renamed to xapi-storage-script, and that original build artifact is run as main.exe --help=groff to produce the manpage. However, at least the default config file name appears to be derived from argv[0], as the install manpage reads:

OPTIONS
       --config=VAL (absent=/etc/main.exe.conf)
           Location of configuration file

[edwintorok]

Hmm, 'dune' only allows to run executables through their private, not their public name.
One fix might be to rename the private name to match the public one, although that'd require renaming 'main.ml' (not just for xapi-storage-script, but in general).

Actually you can run via the public name if you use 'dune exec ' without ./ in front. Except not for 'xapi-storage-script' because that uses 'install' rules instead of defining a public name.

Can you try whether something like this would work (although might now install the file under 2 names, both bin/ and sbin/):

diff --git a/ocaml/xapi-storage-script/dune b/ocaml/xapi-storage-script/dune
index c319e0b45..7ebfb1287 100644
--- a/ocaml/xapi-storage-script/dune
+++ b/ocaml/xapi-storage-script/dune
@@ -1,5 +1,7 @@
 (executable
   (name main)
+  (public_name xapi-storage-script)
+  (package xapi-storage-script)
   (libraries
     async
     async_inotify
@@ -44,7 +46,7 @@
   (targets xapi-storage-script.8)
   (package xapi-storage-script)
   (deps
-    (:x main.exe)
+    (:x %{bin:xapi-storage-script})
   )
   (action (with-stdout-to %{targets} (run %{x} --help=groff)))