unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: Josselin Poiret <dev@jpoiret.xyz>, Wilko Meyer <w@wmeyer.eu>,
	Leo Famulari <leo@famulari.name>,
	guix-devel@gnu.org
Subject: Re: Updates for Go
Date: Mon, 28 Aug 2023 09:14:36 -0600	[thread overview]
Message-ID: <54533df7-46f6-c5a3-f957-411941e2373b@gmail.com> (raw)
In-Reply-To: <87jztiir2g.fsf@protonmail.com>

On 8/25/23 6:29 PM, John Kehayias wrote:
> I've not been following in detail this discussion, but where do we currently stand? Is the proposed Go 1.21 patch basically ready?

As far as I know, yes. I've been using it locally since I submitted the 
patch, and things seem to be working as expected. I think the Guile code 
still needs a review, but as far as I know, it's a pretty standard package.

> Should we create a branch and build job to start seeing how far we get in making 1.21 the default Go in Guix?

I think we should do a two-phase process:

1. Check the package in.

2. Begin working on making it default.

There is utility in having the package available for people to use prior 
to it being the default.

> Like others, I have a few random Go packages (a bunch locally I really need to clean up too) and am not familiar with the language and our packaging much. Still, if I can help review/push some patches and get things moving, please let me know.

The following would help:

1. Testing that the new package behaves correctly for them

2. Submitting individual patches for packages they work with to manually 
specify Go v1.21.0 as the version to use. We can then remove this later.

3. Investigating what work will need to be done for our larger Go 
packages with many leaves.

4. Setting up a Go branch to do the work to cut everything over (I've 
volunteered to do this, but I don't know much about it, so if someone 
does and gets to it first that will be a pleasant surprise!).

> And thanks for all your work here, it is appreciated!

You're welcome! Thanks for asking!

--

Katherine



  reply	other threads:[~2023-08-28 16:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26  0:29 Updates for Go John Kehayias
2023-08-28 15:14 ` Katherine Cox-Buday [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-15 19:57 Katherine Cox-Buday
2023-08-16 17:25 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-17 14:25   ` Katherine Cox-Buday
2023-08-17 21:54     ` Wilko Meyer
2023-08-18  1:52       ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-08-19 11:31       ` Attila Lendvai
2023-08-21 18:14         ` Katherine Cox-Buday
2023-08-21 16:10       ` Katherine Cox-Buday
2023-08-21 17:53         ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-21 18:17           ` Katherine Cox-Buday
2023-08-22  9:59           ` Josselin Poiret
2023-08-22 13:14             ` Attila Lendvai
2023-08-22 14:24               ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-23 16:12                 ` Katherine Cox-Buday
2023-08-27 15:41               ` wolf
2023-08-28 15:18                 ` Katherine Cox-Buday
2023-08-22 11:01         ` Wilko Meyer
2023-08-22 18:06     ` david larsson
2023-08-23 15:35       ` Katherine Cox-Buday

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=54533df7-46f6-c5a3-f957-411941e2373b@gmail.com \
    --to=cox.katherine.e@gmail.com \
    --cc=dev@jpoiret.xyz \
    --cc=guix-devel@gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=leo@famulari.name \
    --cc=w@wmeyer.eu \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).