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
The goal of this ticket is to use opam's solver to produce build plans and save them to our lock files. I imagine the following steps at moment, but this is all subject to change. Our focus should be to get the pipeline working at firs.
Add a command dune pkg lock (name is tentative) to run this step. This command should not build anything and therefore not acquire the build lock.
The command will produce or overwrite dune.lock with the build plan.
We'll need to write some conversion functions from opam's internal metadata into our lock file format. We don't yet support all of opam's features, so this will be incomplete.
Any configuration for this command such as constraints we pass to the solver should be stored in the dune-workspace file.
For now, we can piggy back on opam's repository handling. So to update the repository used as input for lock file generation, we need to run opam update. This is just a temporary step to make implementing this prototype easier.
The text was updated successfully, but these errors were encountered:
The goal of this ticket is to use opam's solver to produce build plans and save them to our lock files. I imagine the following steps at moment, but this is all subject to change. Our focus should be to get the pipeline working at firs.
Add a command
dune pkg lock
(name is tentative) to run this step. This command should not build anything and therefore not acquire the build lock.The command will produce or overwrite
dune.lock
with the build plan.We'll need to write some conversion functions from opam's internal metadata into our lock file format. We don't yet support all of opam's features, so this will be incomplete.
Any configuration for this command such as constraints we pass to the solver should be stored in the dune-workspace file.
For now, we can piggy back on opam's repository handling. So to update the repository used as input for lock file generation, we need to run
opam update
. This is just a temporary step to make implementing this prototype easier.The text was updated successfully, but these errors were encountered: