From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Go build system updates and future work?
Date: Thu, 14 Mar 2019 15:52:24 -0400 [thread overview]
Message-ID: <20190314195224.GA18712@jasmine.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
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.
This fixes the issue of spurious store references
<https://bugs.gnu.org/33620> and should dramatically reduce the closure
size of certain Go packages. So now there is less reason to use bundled
libraries for Go programs.
I think we should consider another change in how we build Go software:
let's stop splitting up Go libraries instead sub-packages.
For example, the packages 'go-golang-org-x-net-ipv4' and
'go-golang-org-x-net-ipv6' are both from the same Git repo at
<https://go.googlesource.com/net>. We should just package
'go-golang-org-x-net'. It's unidiomatic to split them up. In practice, a
Go programmer would have cloned the Git repo into their Go workspace,
and would never have a "split view" of the x/net libraries.
Thoughts? I can work on this in the next week.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-03-14 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 19:52 Leo Famulari [this message]
2019-03-14 22:51 ` Go build system updates and future work? 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
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=20190314195224.GA18712@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
/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).