From: Leo Famulari <leo@famulari.name>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: 34752-done@debbugs.gnu.org
Subject: bug#34752: Duplicated work (sorry!)
Date: Mon, 18 Mar 2019 16:14:19 -0400 [thread overview]
Message-ID: <20190318201419.GB5501@jasmine.lan> (raw)
In-Reply-To: <87imwi2zs6.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
On Sat, Mar 16, 2019 at 05:57:29PM -0500, Katherine Cox-Buday wrote:
> Hey Leo, I've just submitted patch 34887. I didn't realize your patch
> existed until I had already submitted. I apologize, I don't contribute
> to projects managed in this style enough to have the workflow
> internalized :(
It's okay. Our work overlapped but we can consider it a very in-depth
code review :)
> At any rate, my patch does much the same thing except that it leaves
> 1.11 in place as default. I did that for a couple of reasons:
>
> - In organizations, it's very common for projects/teams to lag behind a
> bit the newest releases, and for people installing Go through Guix,
> it's nice to still have previous versions available. The Go team
> officially supports LATEST-2 releases, and I think we should consider
> doing the same.
Okay, let's do this from now on. We can make Go 1.12 the default later.
> - https://golang.org/doc/go1.12#gocache states that the build cache is
> now required. I saw that you were experimenting with setting the home
> directory to `/tmp`. The approach I considered taking was to modify
> the Go build-system to override the `GOCACHE` environmental variable
> when doing builds. Otherwise, any Go package will have to spoof the
> home directory.
Yeah... as discussed on IRC #guix yesterday, we have some work to do to
fully support recent Go.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-03-18 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 22:28 [bug#34752] [PATCH] WIP: Update Go to 1.12 Leo Famulari
2019-03-16 22:57 ` [bug#34752] Duplicated work (sorry!) Katherine Cox-Buday
2019-03-18 20:14 ` Leo Famulari [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190318201419.GB5501@jasmine.lan \
--to=leo@famulari.name \
--cc=34752-done@debbugs.gnu.org \
--cc=cox.katherine.e@gmail.com \
/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.