-
Notifications
You must be signed in to change notification settings - Fork 358
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
opam init --reinit without -ni has a confusing UI #5702
Comments
Is it related to 1dfd536 ? |
That looks to be indeed a regression in 2.2. I’ve added it to the todo list. |
Nevermind it’s not a regression. I can’t reproduce. I think i used
I’m still keeping this issue opened as I think the interface on reinit is not the best but removed it from the 2.2 as it is not an issue for the release. I’ll rename the issue. |
Whenever someone upgrades opam and does
opam init --reinit -ni
(as done in the install.sh script provided), the${OPAMROOT}/opam-init/env_hook.{,z,c}sh
file is removed and thus now users have to calleval $(opam env)
manually.This is because
opam init --reinit
by itself does not take into account what is was configured and reconfigures the env hook again, which removes it if it exists already.Expected behaviour: By default
opam init --reinit
should always keep what was configured, thus-n
shouldn't be needed anymore in the install script.The text was updated successfully, but these errors were encountered: