Remove and install when updating instead of replacing files #601
Comments
This was referenced Nov 9, 2020
jorgebucaran
added a commit
that referenced
this issue
Nov 9, 2020
- Remove and install when updating instead of replacing files (#601) - Updating shouldn't remove plugin if the host is unvailable (#602) - Can't reliably update local plugins because of symlinks (#603) - Filter duplicates in argv and fish_plugins (#604) - Add support to install plugins from branch names with slashes (#588)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Updating a plugin should fetch its latest version, and if that's successful, remove the old and install the new version, instead of trying to overwrite files.
Let's say we install some
my/foobarwhich adds afoobar.fishand_foobar_bazinga.fishto ourfunctions/. If wefisher update my/foobarwhen a new version offoobaris published that no longer has a_foobar_bazinga.fish, Fisher won't be able to remove_foobar_bazinga.fish, since the file won't be in the source directory.This problem exists for both remote and local plugins, but it's even worse for local plugins because we use symlinks for them.
The text was updated successfully, but these errors were encountered: