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
In #307 we discussed how to make the lockfiles reproducible in the presence of command line options (that are able to change the output of the lockfile in a non-trivial way). A compromise that would allow both people to overwrite values via the CLI and yet give hints how to reproduce the generated lockfile is to write the invocation of the opam-monorepo call that was used to create the lockfile into the lockfile itself.
The potential advantages are:
It allows people who want to reproduce the lock file to reproduce it. At least provided they use the same version of opam-monorepo but we don't really provide cross-version reproducibility for plenty of good reasons.
It serves as documentation how the lockfile came to be, so newcomers to a project using opam-monorepo are aware of it and due to the invocation written there, they have a pointer to see how to use opam-monorepo
While this feature will not be implemented in #307, this issue was created to keep track of the idea.
The text was updated successfully, but these errors were encountered:
In #307 we discussed how to make the lockfiles reproducible in the presence of command line options (that are able to change the output of the lockfile in a non-trivial way). A compromise that would allow both people to overwrite values via the CLI and yet give hints how to reproduce the generated lockfile is to write the invocation of the
opam-monorepo
call that was used to create the lockfile into the lockfile itself.The potential advantages are:
opam-monorepo
but we don't really provide cross-version reproducibility for plenty of good reasons.opam-monorepo
are aware of it and due to the invocation written there, they have a pointer to see how to useopam-monorepo
While this feature will not be implemented in #307, this issue was created to keep track of the idea.
The text was updated successfully, but these errors were encountered: