unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: David Dashyan <mail@davie.li>
Cc: 45161@debbugs.gnu.org
Subject: [bug#45161] [PATCH 1/1] gnu: Update go
Date: Thu, 10 Dec 2020 12:43:32 -0500	[thread overview]
Message-ID: <X9JeRHsPtGeLlbcB@jasmine.lan> (raw)
In-Reply-To: <20201210151755.25621-1-mail@davie.li>

On Thu, Dec 10, 2020 at 06:17:55PM +0300, David Dashyan wrote:
> -(define-public go-1.14
> +(define-public go-1.15
>    (package
>      (inherit go-1.4)
>      (name "go")
> -    (version "1.14.10")
> +    (version "1.15.6")

Thanks! I'm doing some tests now. As Jack said, we'll need to update the
'go' package as well in order for this to take effect.

Depending on whether or not the Go packages work with 1.15, we might
need to keep 1.14 around for a while.

For example, check out a Git worktree at commit
18199da4b79ce79d5002c3290cc1fa95454d92ce (gnu: Add Go 1.12.)

In that commit, we added 1.12 but kept 1.11 as the default Go compiler.

$ git worktree add /tmp/guix-multiple-go-compilers 18199da4b79ce79d5002c3290cc1fa95454d92ce && cd /tmp/guix-multiple-go-compilers




  reply	other threads:[~2020-12-10 17:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 15:10 [bug#45161] [PATCH 0/1] Update go? David Dashyan
2020-12-10 15:17 ` [bug#45161] [PATCH 1/1] gnu: Update go David Dashyan
2020-12-10 17:43   ` Leo Famulari [this message]
2020-12-13 21:31     ` David Dashyan
2020-12-10 17:13 ` [bug#45161] [PATCH 0/1] Update go? Jack Hill
2020-12-10 17:37 ` Leo Famulari
2020-12-11  6:15   ` Jack Hill
2020-12-12 22:51     ` Jack Hill
2020-12-13 21:57     ` David Dashyan
2020-12-14 13:10       ` David Dashyan
2020-12-14 21:53       ` Jack Hill
2020-12-13 21:34 ` [bug#45161] [PATCH] gnu: Add go-1.15 David Dashyan

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=X9JeRHsPtGeLlbcB@jasmine.lan \
    --to=leo@famulari.name \
    --cc=45161@debbugs.gnu.org \
    --cc=mail@davie.li \
    /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).