buildDunePackage: use dune install instead of opaline #106150
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
By using
dune install
overopaline
, we makedune
(and of courseocaml
andfindlib
) the sole "static" dependency of any dune package and thus get rid of circular dependency (or bootstrapping) issues because ofopaline
. More specifically: currently we need to buildopaline
and all its dependenciesopam-file-format
withoutdune
. Also we can't enable tests foropam-file-format
sincealcotest
is built usingbuildDunePackage
. This would be no issue if we use dune's install implementation.I've tested this change using
nixpkgs-review
so far and it doesn't break anything new in the standardocamlPackages
set.I'm wondering whether this should be PR'd against
staging
rather thanmaster
since it changes around 600 ocamlPackages which all exist in multiple versions.Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)