A workaround is to just ignore these vendored dependencies and rely on dune to pick them up when building.
However if the vendored dependencies are modified to depend on an additional package these won't be picked up and will have to manually be added to the query.
Is your feature request related to a problem? Please describe.
My motivation is picking up vendored dependencies in materialization.
Describe the solution you'd like
For
opam-nix-gen
support picking up multiple packages in the same project.An
materializeOpamProject'
could be useful for this. Something like:Describe alternatives you've considered
A workaround is to just ignore these vendored dependencies and rely on dune to pick them up when building.
However if the vendored dependencies are modified to depend on an additional package these won't be picked up and will have to manually be added to the query.
Additional context
I came about this limitation while working on https://github.com/RyanGibb/aeon, which has dependencies vendored: https://github.com/RyanGibb/aeon/tree/e28f84281886394e81ba07076de21b3725aa7eec/duniverse.