all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pier-Hugues Pellerin <ph@heykimo.com>
To: 55210@debbugs.gnu.org
Cc: Pier-Hugues Pellerin <ph@heykimo.com>
Subject: [bug#55210] [PATCH 0/3] Add go-1.18.1
Date: Sun,  1 May 2022 14:55:55 -0400	[thread overview]
Message-ID: <20220501185555.26169-1-ph@heykimo.com> (raw)

Hello,

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[0].

- 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.

Thanks everyone

ph

[0] https://github.com/golang/go/issues/44505


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(+)

-- 
2.35.1





             reply	other threads:[~2022-05-01 18:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 18:55 Pier-Hugues Pellerin [this message]
2022-05-01 18:57 ` [bug#55210] [PATCH 1/3] gnu: Add go-1.18 Pier-Hugues Pellerin
2022-05-01 18:58 ` [bug#55210] [PATCH 2/3] gnu: Add go-next Pier-Hugues Pellerin
2022-05-01 18:58 ` [bug#55210] [PATCH 3/3] gnu: go: Update to go-1.18 Pier-Hugues Pellerin
2024-01-31 20:53 ` bug#55210: [PATCH 0/3] Add go-1.18.1 Sharlatan Hellseher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220501185555.26169-1-ph@heykimo.com \
    --to=ph@heykimo.com \
    --cc=55210@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.