We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is a tracking issue for possible residual behaviour in 2.1 from opam 2.0's base packages which don't make sense in 2.1 with switch invariants.
OpamClient.fixup
OpamClient.install_t
OpamSwitchCommand.install_compiler
The remaining three items are not critical for 2.1.0. However, we should also consider:
Do we still need to care about the compiler flag in the same way?
compiler
The text was updated successfully, but these errors were encountered:
Fixed with #4623
Sorry, something went wrong.
AltGr
dra27
No branches or pull requests
This is a tracking issue for possible residual behaviour in 2.1 from opam 2.0's base packages which don't make sense in 2.1 with switch invariants.
OpamClient.fixup
- base message in there, does it just want rewording? - Update remaining references to base packages #4623OpamClient.install_t
- updating the installed automatically state of base packages. That no longer matters? - Update remaining references to base packages #4623OpamSwitchCommand.install_compiler
- "Could not resolve base install" and "base package installs". I expect these messages just need re-wording. - Update remaining references to base packages #4623The remaining three items are not critical for 2.1.0. However, we should also consider:
Do we still need to care about the
compiler
flag in the same way?The text was updated successfully, but these errors were encountered: