Closed yurivict closed 2 years ago
Ah, yes, Go requires version tags to either start with ie.1
or v
, but never 2
.
I added a v2.43.1
tag. Did that help?
It would be possible to say with the next release if that helped.
Thanks for reporting. Please re-open this issue if it's still a problem with the next release.
The module URL github.com/xyproto/o should end with /v2 for Google servers to pick up the project.
This is still an issue.
But reading the documentation for v2: https://go.dev/blog/v2-go-modules, it seems to me that it only applies to modules.
o
is not a Go module, though. It only has a main
package, and compiles down to an executable.
Is there a benefit to either removing all v2*
tags (which I won't do) or moving all source code into a v2
directory (which I might, but it does not feel like a clean solution)?
I started moving all source files, go.mod
and go.sum
to v2/
, which only lives in the v2
branch, for now.
Is the script also meant for executables (package main
), or only for Go modules?
But reading the documentation for v2: https://go.dev/blog/v2-go-modules, it seems to me that it only applies to modules.
No, it applies to applications too.
Go projects are downloaded by the FreeBSD framework from Go servers, otherwise dependencies are often messed up.
I tried all sorts of things.
Does it work now?
https://index.golang.org/index?limit=1&since=2022-02-09T17:29:00Z
1.2.48 is backwards from 2.47.0.
You need to add /v2 to the module URL.
Thanks for the help.
I think it might be fixed now. I added a /v2
directory and added /v2
to go.mod:
https://index.golang.org/index?limit=1&since=2022-02-10T09:53:00Z
go install github.com/xyproto/o/v2@latest
also works here now.
Assuming this works now.
I had never imagined that versioning over 1.0 would be so logistically demanding.
Assuming this works now.
It works, thanks!
I had never imagined that versioning over 1.0 would be so logistically demanding.
Large companies produce poor quality code. That's surprising!
I use this script to retrieve versions:
This script shows "o" versions that aren't in the same format as
2.43.1
:Correct version isn't being picked up for some reason.