If there were installs from the prior v-analyzer repo running v-analyzer up can currently cause several issues.
For a reproduction, put the install script of the old repo into v-analyzers (old install script: https://github.com/v-analyzer/v-analyzer/blob/main/install.vsh) config dir (e.g. ~/.config/v-analyzer/install.vsh). That's the location that v-analyzer is currently looking for a script and it won't fetch a fresh script when it finds it.
Then running v-analzyer up - even with the latest nightly version - It will "update" / "downgrade" to the latest release of the old repo.
To fix this, and to also get advantages of potential fixes and updates to the install script now will always fetch the latest install script for an installation of a release or nightly version.
The fix will work after using a new binary that contains the changes in this PR.
Fixes #11
If there were installs from the prior v-analyzer repo running
v-analyzer upcan currently cause several issues.For a reproduction, put the install script of the old repo into v-analyzers (old install script: https://github.com/v-analyzer/v-analyzer/blob/main/install.vsh) config dir (e.g.
~/.config/v-analyzer/install.vsh). That's the location that v-analyzer is currently looking for a script and it won't fetch a fresh script when it finds it. Then runningv-analzyer up- even with the latest nightly version - It will "update" / "downgrade" to the latest release of the old repo.To fix this, and to also get advantages of potential fixes and updates to the install script now will always fetch the latest install script for an installation of a release or nightly version.
The fix will work after using a new binary that contains the changes in this PR.