-
Notifications
You must be signed in to change notification settings - Fork 454
Future plans for GoVersion #297
Comments
It's used in the heroku buildpack to determine what version of go should be used to compile the provided code. I have thought about doing something similar in the heroku buildpack (where '1.4.*' would mean the latest patch revision of 1.4'. Beyond that I consider it an optional field as godep really shouldn't be involved with compiling code in any way in the long term. But also note that godep will update that value if you save and are running a newer version. |
Thanks for the info. The CF buildpacks are downstream of the Heroku ones, so it might be possible for us to do this in the upstream repo and send you a PR, if you're interested. |
That would be great! |
@freeformz, can we clarify about the wildcard. We'd like to support it for patch level, not minor/major. I'll reopen this on the buildpack's issues. |
Are there plans for
godeps
to useGoVersion
other than just recording it?We're asking because we (Cloud Foundry buildpacks team) are planning to allow users to specify their go version like
This will allow a user to get the latest patch version of go during staging, instead of getting a staging error due to unsupported versions. However, if there are plans for godeps to use this field, our use could break. Thanks for any info!
The text was updated successfully, but these errors were encountered: