unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pier-Hugues Pellerin <ph@heykimo.com>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Updating from Go 1.17 to 1.18
Date: Sun, 1 May 2022 15:07:20 -0400	[thread overview]
Message-ID: <CA+RyfLkKUgPcjmgtOP_dWCEJBZ3ytg1YzJrcBx-2GvUEtHYKSA@mail.gmail.com> (raw)
In-Reply-To: <87sfq6xz3v.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]

Hello Katherine and Ludovic,

I've finally had the time to push the patches[0], my house was hit hard by
sickness.

Concerning having Go 1.18 as the default version, I think it's on Ludovic
side to create a
branch to see where things breaks..

Not sure where the outputs will be but I am sure we will have a few
dependencies to fix
It will be good to work together to fix them.

Thanks



[0] https://issues.guix.gnu.org/55210

On Thu, Apr 21, 2022 at 10:58 AM Katherine Cox-Buday <
cox.katherine.e@gmail.com> wrote:

> Pier-Hugues Pellerin <ph@heykimo.com> writes:
>
> > We should probably also try to mimic how their bootstrap and have the
> > following:
> >
> >    - Bootstrap 1.17 with 1.4
> >    - Bootstrap 1.18 with 1.4
> >    - Have 1.19 bootstrap with 1.17.
> >
> > So maybe we should do something like this.
> >
> > - Add go-1.18 build from 1.4.
> > - Add go-next that point to go-1.18
> > - Refactor 1.17 package definition that is shared between go-1.18. and
> > go-1.17.
> > - Move  go to go-1.18  in another branch
> > - Remove 1.16?
>
> Thanks for looking into how the Go team will be bootstrapping, and I
> agree with your plan. Is there anything I can do to help?
>
> --
> Katherine
>


-- 
ph

[-- Attachment #2: Type: text/html, Size: 2030 bytes --]

      reply	other threads:[~2022-05-01 19:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 19:45 Updating from Go 1.17 to 1.18 Pier-Hugues Pellerin
2022-04-10 20:45 ` Ludovic Courtès
2022-04-10 21:16   ` Pier-Hugues Pellerin
2022-04-20 23:36     ` Katherine Cox-Buday
2022-04-20 23:43       ` Pier-Hugues Pellerin
2022-04-21  0:24         ` Pier-Hugues Pellerin
2022-04-21 14:58           ` Katherine Cox-Buday
2022-05-01 19:07             ` Pier-Hugues Pellerin [this message]

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=CA+RyfLkKUgPcjmgtOP_dWCEJBZ3ytg1YzJrcBx-2GvUEtHYKSA@mail.gmail.com \
    --to=ph@heykimo.com \
    --cc=cox.katherine.e@gmail.com \
    --cc=guix-devel@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 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).