-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Pkg.update("Foo") to update a single package only? #13487
Comments
(It's also a lot faster to update only a single package. It's frustrating to wait for 50 packages to update if all I wanted was a newer version of IJulia, for example.) |
+1 (btw: if you had asked me earlier, i would have been 99% sure, that this already exists...) |
💯 |
While this sounds like a good idea, I think either |
+1 to @simonster's sentiment - I think this needs to also recursively update dependencies, given how careful people are with their REQUIRE files. |
Oh yeah definitely! Anything else wouldn't make much sense. |
See #17132. |
It would be very useful to have a
Pkg.update("Foo")
that only updates a single packageFoo
and its dependencies. It's very common to want to get the latest tagged version of a specific package (notmaster
) but not want to update everything on your system for fear of breaking something (especially user code).Even better, only update its dependencies if a specific version is
REQUIRE
d, and then only update to the minimum version required.(Nor should this result in pinned packages; I still want
Pkg.update()
to update everything.)In an ideal world, no one would ever tag a buggy version of a package, and no one would ever update APIs in ways that break user code, but we don't live in that world And yes, there is
Pkg.pin
, but that is opt-out of updates one package at a time, but this is painful if you want to pin lots of packages—what I want is opt-in updating, and I still want to be able to doPkg.update()
when I'm ready to update everything (without going back and freeing all the pinned packages).The text was updated successfully, but these errors were encountered: