> It seems that location for ocaml libs is in $(OCAMLDESTDIR), any reason > to deviate from that?
OCAMLDESTDIR is only defined in tools/ocaml/common.make, and is unavailable at the top-level directories level of the autoconf infrastructure (which generates the paths.ml file), as far as I understand. > Is there any reason to put that new library in "/usr/libexec"? > It doesn't seems like a good place for it, and using "/usr/lib" instead > seems better. I find that the general idea of libexec - that only a particular program (oxenstored) relies on this and others should not - fitting for this use case. It will additionally distinguish between the plugin itself and the packaged plugin interface (that will go into OCAMLDESTDIR, as suggested elsewhere in the review comments) > libexec is mostly for binary, according to > https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html Even though the .cmxs is a shared object, it will run some of its own code to "link" itself to the global ref defined in the plugin interface, even without anyone calling into the library, sort of behaving like a binary.
