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
Opam is allowed to include files and their checksums in <pkgname.config>. E.g.:
file-depends: [
[ "/foo/bar" "checksum" ]
]
This is basically a dynamic dependency mechanism like in our dynamic action plugin. We can discard the hash and just add a dependency on the file in question.
The text was updated successfully, but these errors were encountered:
When do we add the dependency? The .config files exist in the sources of the repos themselves, sometimes even being generated using .in files.
This means that we cannot add this dependency in the lock file for the package. The build step could generate the config files so it might be possible to include the dependency then. Or the install step might be an ideal place to do it.
As an update I had a go at this, but from what I understand there doesn't seem to be a way to add dynamic dependencies to custom actions. Notably, dune_action_plugin is using it's own thing. There appears to be a CR in action_intf about adding such a "needs more dependencies" result in the action part of a custom action.
Opam is allowed to include files and their checksums in
<pkgname.config>
. E.g.:This is basically a dynamic dependency mechanism like in our dynamic action plugin. We can discard the hash and just add a dependency on the file in question.
The text was updated successfully, but these errors were encountered: