Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.0.10 Backported commits #4874

Merged
merged 10 commits into from
Oct 29, 2021
Merged

2.0.10 Backported commits #4874

merged 10 commits into from
Oct 29, 2021

Conversation

rjbou
Copy link
Collaborator

@rjbou rjbou commented Oct 19, 2021

Todo

Pull requests

@rjbou rjbou added this to the 2.0.10 milestone Oct 19, 2021
@rjbou rjbou added this to In Progress in Opam 2.0.x via automation Oct 19, 2021
For environment variables which can be split (e.g. `PATH` on `:`),
OpamEnv.unzip_to attempts to find the point in the variable at which a
value was added. This is fine if a _single_ value was added, but fails
if the addition was multiple values (for example, if a setenv
instruction added two directories to `PATH` in one `+=`).

This is fixed by first splitting the value being searched according to
the same rule as the environmen variable and ensuring they all match in
order.
rjbou and others added 8 commits October 29, 2021 11:42
When a package is installed, the switch environment is recomputed and
written, but if the setenv fields referred to package variables just
written to .config then these weren't available as the switch state
didn't include the new config file.

Subsequent calls to opam would then fix the issue as the .config file
will have been loaded with the switch state.
@rjbou rjbou merged commit 7d4a0f2 into ocaml:2.0 Oct 29, 2021
Opam 2.0.x automation moved this from In Progress to Done Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants