cli: Anchor version manager (avm) #1385
Merged
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
|
Here is the commit with the documentation. I've pulled it out of this PR since the |
Awesome let's add that PR to the book repo. |
|
Should we use this in CI to install anchor? I think probably. |
|
@tomlinton we are deprecating /docs yes. you can add the documentation to the seperate anchor-book repo |
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.
Adds the command line util
avmand a wrapperanchorbinary that runs the correct version of anchor-cli. Usage is explained in the docs.Looks like book just got removed from this repo. I'll make a new PR for this documentation in the anchor-book repo. Are we deprecating the
docs/directory or should I also add it there?I'm not sure how to version
avm, we might sync it with the main anchor version, or perhaps avm should live in a separate repo since tagging will get messy.There is other approaches apart from using the wrapper binary, e.g. asking the user to set PATH to the ~/.avm/bin directory or using symlinks. The wrapper seemed like the nicest approach to me.
Closes #586.