PPier-Hugues Pellerin wrote on 1 May 2022 20:55
(address . email@example.com)(name . Pier-Hugues Pellerin)(address . firstname.lastname@example.org)
I've added a go 1.18 package, still learning the build and all the quirks. So far I've did
the following in multiple commits, I hope it's okay:
- I've created a new go-1.18 package inheriting from 1.17.
This mean that the build use the same logic as before, use go 1.4 for the build toolchain.
and fallback on previous version 1.17
- I've changed the Homepage of the Go 1.18 package.
Guix lint complained about a change in the URL, so I've updated it to https://go.dev.
- 1.17 is here to stay for some time
I've looked at the toolchain of the Go language, today the minimun version of go require to build is
1.4, but this will be updated to 1.17 for 1.19.
- Adding go-next to point to go 1.18.
Following a discussion on email I've added `go-next` that currently point to 1.18,
I've copied the strategy from the emacs' package that also define an emacs-next
package to allow users to try out the latest version. I am not sure this was the right way
to do it. I
- Made go point to 1.18 as the default version
Following Ludovic advice I've made the default go point to 1.18, so we can create a testing branch and see
what is failling.
Pier-Hugues Pellerin (3):
gnu: Add go-1.18.
gnu: Add go-next.
gnu: go: Update to go-1.18
gnu/packages/golang.scm | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)