analyzer: use latest install script when updating #81
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 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.