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

Prioritize higher versions of direct dependencies over indirect dependencies #4043

Open
KristofferC opened this issue Oct 11, 2024 · 1 comment
Labels

Comments

@KristofferC
Copy link
Member

Right now, you can end up in a situation where you have, say Plots, installed at some version but you can force it to be at an even higher version at the cost of downgrading some transitive dependencies:

(@v1.10) pkg> add [email protected]
   Resolving package versions...
    Updating `~/.julia/environments/v1.10/Project.toml`
  [91a5bcdd] ↑ Plots v1.40.1 ⇒ v1.40.8
    Updating `~/.julia/environments/v1.10/Manifest.toml`
  [b99e7846] - BinaryProvider v0.5.10
  [c87230d0] ↑ FFMPEG v0.2.4 ⇒ v0.4.2
  [91a5bcdd] ↑ Plots v1.40.1 ⇒ v1.40.8
⌅ [b22a6f82] ↓ FFMPEG_jll v6.1.2+0 ⇒ v4.4.4+1
⌅ [1270edf5] ↓ x264_jll v10164.0.0+0 ⇒ v2021.5.5+0
⌅ [dfaa095f] ↓ x265_jll v3.6.0+0 ⇒ v3.5.0+0

In some sense, direct dependencies are more important and it is likely that you want to prioritize those having a higher version over e.g. FFMPEG here.

Would it be possible to incorporate something like that into the resolver, @carlobaldassi

@IanButterworth
Copy link
Member

I think this is a better more general approach of what #3898 is proposing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants