Add support for choosing what binary to run with mage #146
Conversation
This file contains hidden or 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.
It's easy these days to install multiple versions of go side by side, using
go get golang.org/dl/go1.11etc. So, let's support those in Mage! With this PR you can choose what go binary to use by setting MAGEFILE_GOCMD to the name/path of the binary.This also allows you use the same variable to choose what version of go to compile mage itself with if you use the magefile to compile.
Finally, we now embed the version of go used to compile mage itself in the
mage -versionoutput, which can be useful to understand what mage is doing.