Closed nojb closed 5 years ago
Isn't it already in a separate package? If you don't depend on ocamlbuild_plugin, it shouldn't introduce issues when vendoring.
Not sure why, but it does, regardless of whether you depend on it or not... I will give it a closer look tomorrow and report back here.
Why do you say it is a separate package?
It's in this package, isn't it? https://github.com/ocaml-ppx/ocaml-migrate-parsetree/blob/master/ocaml-migrate-parsetree-ocamlbuild.opam
I suppose the issue is that when you vendor it, then the @install
alias picks up both packages.
Yes, I just arrived at the same conclusion.
What would be the best way to handle this?
@rgrinberg has a proposal for explicitly marking the vendored directory: https://github.com/ocaml/dune/issues/1016. The idea would be that aliases such as @install
wouldn't pick up things in the vendor directory: only what's needed from the vendor directory would be built.
Sounds reasonable, so closing this one. Thanks!
This one-liner simply makes the building of
ocamlbuild_plugin
optional, which allows to vendorocaml-migrate-parsetree
withoutocamlbuild
.