From: Leo Famulari <leo@famulari.name>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Packaging gx (for IPFS): Need to update default Go to 1.11?
Date: Wed, 7 Nov 2018 15:40:54 -0500 [thread overview]
Message-ID: <20181107204054.GA29657@jasmine.lan> (raw)
In-Reply-To: <87efbwmyyz.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
On Wed, Nov 07, 2018 at 09:09:24PM +0100, Pierre Neidhardt wrote:
> Sure, but isn't this too much a hassle (and more pollution added to the package
> namespace) for a temporary workaround?
It's a matter of taste :)
> Shouldn't we focus on fixing the cache bug in the build system instead?
Yes, we should, but that problem is not related to packages not building
with Go 1.11 because they need to be updated upstream, right? Even if
our go-build-system was updated, those packages would still need to be
built with Go 1.9? Or did I misunderstand?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-07 20:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 11:40 Packaging gx (for IPFS): Need to update default Go to 1.11? Pierre Neidhardt
2018-10-24 11:42 ` Pierre Neidhardt
2018-10-24 13:55 ` Leo Famulari
2018-10-24 14:02 ` Pierre Neidhardt
2018-10-24 14:14 ` Leo Famulari
2018-11-06 11:56 ` Pierre Neidhardt
2018-11-06 12:03 ` Pierre Neidhardt
2018-11-06 17:04 ` Pierre Neidhardt
2018-11-06 17:31 ` Leo Famulari
2018-11-06 17:33 ` Pierre Neidhardt
2018-11-06 19:57 ` Leo Famulari
2018-11-07 7:33 ` Pierre Neidhardt
2018-11-07 16:22 ` Pierre Neidhardt
2018-11-07 18:26 ` Leo Famulari
2018-11-07 20:09 ` Pierre Neidhardt
2018-11-07 20:40 ` Leo Famulari [this message]
2018-11-07 20:48 ` Pierre Neidhardt
2018-11-07 21:03 ` Leo Famulari
2018-11-11 16:43 ` Pierre Neidhardt
2018-11-11 20:52 ` Pierre Neidhardt
2018-11-11 21:33 ` Pierre Neidhardt
2018-11-12 9:45 ` Pierre Neidhardt
2018-11-12 17:33 ` Leo Famulari
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=20181107204054.GA29657@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).