From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Go build system updates and future work?
Date: Fri, 15 Mar 2019 21:40:15 -0500 [thread overview]
Message-ID: <87r2b735kg.fsf@gmail.com> (raw)
In-Reply-To: <20190314195224.GA18712@jasmine.lan> (Leo Famulari's message of "Thu, 14 Mar 2019 15:52:24 -0400")
Leo Famulari <leo@famulari.name> writes:
> I just pushed a revamped Go build system with commit
> e3900a4d64e4bf6f426809d6bff058e5a2ae9bc8.
>
> The main change is that instead of putting the list of Go-language
> dependencies store paths in the GOPATH environment variable, these store
> paths are union-symlinked into the build directory, and GOPATH points
> there.
There is a larger change coming that I think we need to account for. Go
modules are here (and in v1.13 will be on by default). This feature
allows Go code to be built outside of a $GOPATH. I'm unsure how this
information intersects with your work, so I'll just leave a link to the
wiki[1] on modules.
Thank you for your contributions!
[1] - https://github.com/golang/go/wiki/Modules
--
Katherine
next prev parent reply other threads:[~2019-03-16 2:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 19:52 Go build system updates and future work? Leo Famulari
2019-03-14 22:51 ` Pierre Neidhardt
2019-03-14 22:54 ` Pierre Neidhardt
2019-03-14 23:11 ` Leo Famulari
2019-03-16 10:08 ` Christopher Baines
2019-03-14 23:15 ` Leo Famulari
2019-03-15 6:54 ` Pierre Neidhardt
2019-03-16 10:49 ` swedebugia
2019-03-16 2:40 ` Katherine Cox-Buday [this message]
2019-03-17 17:43 ` 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=87r2b735kg.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).