You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that, if a BuildDepends entry appears in an Executable but not in a Library, it is not included in the opam file. For instance, my project includes a single library with the following BuildDepends:
As a result, the OPAM package fails to install unless the user has already manually installed ppx_deriving_yojson. Am I misunderstanding the function of these fields? Is this an oversight?
The above project can be found here. Steps to reproduce:
It seems that, if a
BuildDepends
entry appears in anExecutable
but not in aLibrary
, it is not included in theopam
file. For instance, my project includes a single library with the followingBuildDepends
:It has a single executable with this
BuildDepends
:The resulting
opam
file contains thisdepends
entry:As a result, the OPAM package fails to install unless the user has already manually installed
ppx_deriving_yojson
. Am I misunderstanding the function of these fields? Is this an oversight?The above project can be found here. Steps to reproduce:
The last command will fail with an error message something like this:
Please let me know if I can provide additional information. Thank you for the tool!
The text was updated successfully, but these errors were encountered: