Skip to content
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

Update tags to support Go modules #23

Open
daved opened this issue Mar 4, 2019 · 3 comments
Open

Update tags to support Go modules #23

daved opened this issue Mar 4, 2019 · 3 comments

Comments

@daved
Copy link

daved commented Mar 4, 2019

There may be a workaround, but I'm having a lot of trouble trying to install latest due to the current tags lacking the "v" prefix.

@daved
Copy link
Author

daved commented Mar 4, 2019

Setting GO111MODULE=off is the obvious solution, but I'd rather avoid polluting my GOPATH. I will try with a temporary GOPATH for now.

@davcamer
Copy link
Contributor

davcamer commented Apr 10, 2019

I appear to have successfully done this by running
go get github.com/tiziano88/elm-protobuf@3.0.0

That command added
github.com/tiziano88/elm-protobuf v0.0.5-0.20180917212848-43b6ec64321b
to the require section of my go.mod file.

To "pin" that version (I am also vendoring) I also added a
github.com/tiziano88/elm-protobuf => github.com/tiziano88/elm-protobuf v0.0.5-0.20180917212848-43b6ec64321b
to the replace section of go.mod. This last part is probably unnecessary but I don't want a go mod tidy or other command to reset the version to the seemingly compatible v0.0.4 tag. Since this old tag is in the format that go modules expects, it confuses the tools.

We also have a "tools.go" file as described on the modules wiki.

// +build tools

package grpc

import (
	// We are using 3.0.0 tag of this dependency, but the convention of using a
	// versioned path like "github.com/tiziano88/elm-protobuf/v3" doesn't work.
	// This is expected since it is not (yet?) a proper go module. This is
	// exacerbated by an old "v0.0.4" tag in the repository, which the go tools
	// incorrectly recognize as a pre-release module tag.
	//
	// Instead, there is a replace directive in the go.mod file to pin the
	// correct module incompatible version.
	_ "github.com/tiziano88/elm-protobuf/protoc-gen-elm"
)

I think the newer tags are in the format they are in for the sake of the elm packaging tools. Maybe dual tags are needed? But a go.mod file would be needed as well to really make this compatible with go's packaging tools.

Isn't it funny how Elm packages are to Elm modules the same way go modules are to go packages? 😆

@tiziano88
Copy link
Owner

Thanks for the comments, I have not been following the latest on Go module management, if anyone wants to suggest a fix I am happy to implement it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants