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: Tue, 6 Nov 2018 14:57:12 -0500 [thread overview]
Message-ID: <20181106195712.GB6749@jasmine.lan> (raw)
In-Reply-To: <87k1lqyuta.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
On Tue, Nov 06, 2018 at 06:33:53PM +0100, Pierre Neidhardt wrote:
> > If most of the Go packages are ready for Go 1.11, we could make it the
> > dfeault and then use Go 1.9 for the packages that are lagging behind. Or
> > vice versa.
>
> How do you do that?
The default Go is defined in ((guix build-system go) default-go).
Updates can be tested with this diff:
diff --git a/guix/build-system/go.scm b/guix/build-system/go.scm
index cf9116327..80894677f 100644
--- a/guix/build-system/go.scm
+++ b/guix/build-system/go.scm
@@ -44,7 +44,7 @@
(define (default-go)
;; Lazily resolve the binding to avoid a circular dependency.
(let ((go (resolve-interface '(gnu packages golang))))
- (module-ref go 'go)))
+ (module-ref go 'go-1.11)))
(define* (lower name
#:key source inputs native-inputs outputs system target
And individual packages can be made to use non-default Go compilers with
the #:go key, like this:
diff --git a/gnu/packages/curl.scm b/gnu/packages/curl.scm
index 2fb87251f..4c8c83d84 100644
--- a/gnu/packages/curl.scm
+++ b/gnu/packages/curl.scm
@@ -171,6 +171,7 @@ tunneling, and so on.")
(arguments
`(#:import-path "gitlab.com/davidjpeacock/kurly"
#:install-source? #f
+ #:go ,go-1.11
#:phases
(modify-phases %standard-phases
(add-after 'install 'install-documentation
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-06 20:07 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 [this message]
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
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=20181106195712.GB6749@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).