Skip to content

Fix 'opam install --deps-only .' not doing anything if the package is already installed but not pinned #6504

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

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

kit-ty-kate
Copy link
Member

Fixes #6501

This is a WIP fix for #6501. It currently fixes the main issue (dependencies are not installed when the base package is already installed but not pinned), but does not fix the secondary issue where the base package ends up being removed if the local version has a different version because it internally thinks the package is being pinned.

I'm not sure how to fix that secondary issue yet. @rjbou any idea?

@kit-ty-kate kit-ty-kate added AREA: ENGINE PR: WIP Not for merge at this stage labels May 2, 2025
@kit-ty-kate kit-ty-kate added this to the 2.4.0~alpha2 milestone May 2, 2025
@kit-ty-kate kit-ty-kate modified the milestones: 2.4.0~alpha2, 2.4.0~alpha3 May 5, 2025
@rjbou rjbou self-requested a review May 12, 2025 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AREA: ENGINE PR: WIP Not for merge at this stage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

opam install . --deps-only does nothing when a package of the same name and version is already installed but not pinned
2 participants