-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding custom command #6
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Andrew Steurer <[email protected]> saving work Signed-off-by: Andrew Steurer <[email protected]> saving work Signed-off-by: Andrew Steurer <[email protected]> updating version Signed-off-by: Andrew Steurer <[email protected]>
a90e2c6
to
73c8ecb
Compare
Would it make sense to allow more than one custom build? I for one have aliases for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To @karthik2804's point, it would be
Create/update a pointer to a custom version: | ||
|
||
```sh | ||
spin verman set custom --file path/to/spin/binary |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do paths not have to be absolute?
Create/update a pointer to a custom version: | ||
|
||
```sh | ||
spin verman set custom --file path/to/spin/binary |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar to @karthik2804's point, it would be great to have something along the lines of:
spin verman set <user-chooses-name> /path
verman
would know that it is a custom entry due to the path being provided
No description provided.