-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Cannot install a package at a certain tag #80
Comments
@jeffbyrnes is working on a cleanup with the resource these attributes use in #78. Can you see if this problem still exists using that branch? |
@ramereth Since there is no setting of GO111MODULE to 'on' I would tend to doubt it. I'll give it a shot when I have a moment. |
@grimm26 we can certainly work out a way to include that. I have plans to refactor the cookbook further, and provide for Go modules (since they are how the Go community appears to have decided to move forward). Iβd certainly welcome a PR, too! |
@grimm26 What problem are you trying to solve? Could you add some detail about what result you expect from Thanks, |
@MarkGibbons The problem I am trying to solve is installing
|
Thanks. So in that case it looks like you expect to see the source code loaded in go/pkg/mod/github.com/itpp-labs/[email protected]+incompatible. Seems doable. Making the resource idempotent is a bit of an issue. Have you considered submitting your code as a PR? |
I can submit a PR, but the work I have done in my fork refactored your custom resource, too. |
We can get Markβs work in #82 merged in, then build on that, and release both as v4.1.0 (since it should be non-breaking, with the attributes preserved). |
π» Brief Description
when I specify a package @ a tag, it complains " go: cannot use path@version syntax in GOPATH mode"
π₯ Cookbook version
v3.0.1
π©βπ³ Chef-Infra Version
13.10.0
π© Platform details
ubuntu 18.04
Steps To Reproduce
Steps to reproduce the behavior:
π Expected behavior
get, build, install the binary
β Additional context
Add any other context about the problem here. e.g. related issues or existing pull requests.
The text was updated successfully, but these errors were encountered: