Update specific packages without re-installing everything #527
Comments
|
Will that also allow for a more safe update mode? The single complaint I have with just running Also a question related to this issue: it would be interesting to know if an update was a real update or the same version has simply been reinstalled. |
Hmm, interesting! Thanks for the idea.
I agree that it would, but that's not part of my plan this time. Thanks for the suggestion, though! |
`_update`. Starting with 4.0 plugin authors should be able to reliably know when their plugin is installed, updated, or uninstalled. Related #526, #527 #573. - Remove "some" OMF plugin support (it won't go away completely since more than less of OMF plugins actually work fine). This means fully deprecating `init.fish`, `uninstall.fish`, etc. So long, and thanks for all the fish! Related: #581 - No cache fallback, no plugin dependencies, no more private package hosts, and no more gitlab/bitbucket support. #464, #579 - Require fish 3.0, use newer fish features, e.g., use `wait` to implement concurrent downloads. - Rely less on external tools. No awk, no sed, no basename/dirname. Just mv, rm, cp, and mkdir. Deprecate `fishfile` in favor of `fish_plugins`. This new file works like the old fishfile, but without comment support. See #524.
- Introduce event system. #526, #527 #573. - Deprecate `init.fish`, `uninstall.fish`, etc. #581 - No cache fallback, no plugin dependencies, no more private package hosts, and no more gitlab/bitbucket support. #464, #579 - Require fish 3.0, use newer fish features, e.g., use `wait` to implement concurrent downloads. - Rely less on external tools. No awk, no sed, no basename/dirname. Just mv, rm, cp, and mkdir. - Deprecate `fishfile` in favor of `fish_plugins`. This new file works like the old fishfile, but without comment support. See #524.
- Introduce new event system. #526, #527 #573. - Deprecate `init.fish`, `uninstall.fish`, etc. #581 - No cache fallback, no plugin dependencies, no more private package hosts, and no more gitlab/bitbucket support. #464, #579 - Require fish 3.0, use newer fish features, e.g., use `wait` to implement concurrent downloads. - Rely less on external tools. No awk, no sed, no basename/dirname. Just mv, rm, cp, and mkdir. - Deprecate `fishfile` in favor of `fish_plugins`. This new file works like the old fishfile, but without comment support. See #524.
|
Implemented in 4.x. 🎉 |
Let's add a new command to update packages:
fisher update <package...>.Why? Sometimes you want to update one or more packages without re-installing everything. One of such cases is when developing a local package. After doing it a few times, even waiting a few milliseconds can be annoying.
Using
updatewill download only the specified packages and their dependency trees, reducing the total number of network requests. Updating a package should not trigger apkg_uninstallevent (#526).Still on the table is whether we should emit a new event like
pkg_update. Should we also emit apkg_installevent for newly added packages?I'm not too keen on adding new events, but maintaining consistency is one argument in their favor.
If I decide to add them, they'll probably come in a future minor release after 3.3.0.Coming in 4.0.The text was updated successfully, but these errors were encountered: