From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Golang programs keeping references [gnu: go: Update default to 1.11.]
Date: Fri, 14 Dec 2018 15:52:27 +0100 [thread overview]
Message-ID: <87wooc17pw.fsf@gnu.org> (raw)
In-Reply-To: <87pnu4e9un.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Fri, 14 Dec 2018 10:28:00 +0100")
Pierre Neidhardt <mail@ambrevar.xyz> skribis:
> go-ipfs is fine indeed, but that's because you've just looked at the lucky
> package! go-ipfs vendors all the Go dependencies, which is why there is no
> extra input there and go-ipfs closure size is optimal.
Oh, we should really work towards unbundling things from ‘go-ipfs’. Any
idea how difficult that would be?
> Now try with gx, demlo or syncthing: all of them had zero Go inputs in their
> closure with go-1.9. Now they have hundreds with go-1.11 :(
“guix size syncthing”, for instance, returns mostly tiny Go packages,
which looks good to me, no?
Anyway, if you think there’s a problem, could you email details to
bug-guix@gnu.org so we keep track of it there?
Thanks!
Ludo’.
next prev parent reply other threads:[~2018-12-14 14:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181112093245.26230.94815@vcs0.savannah.gnu.org>
[not found] ` <20181112093246.AC1D620498@vcs0.savannah.gnu.org>
2018-11-12 17:29 ` Golang programs keeping references [gnu: go: Update default to 1.11.] Leo Famulari
2018-11-12 17:38 ` Pierre Neidhardt
2018-11-12 17:45 ` Leo Famulari
2018-11-12 17:48 ` Leo Famulari
2018-11-12 17:51 ` Leo Famulari
2018-12-09 18:46 ` Pierre Neidhardt
2018-12-14 9:15 ` Ludovic Courtès
2018-12-14 9:28 ` Pierre Neidhardt
2018-12-14 14:52 ` Ludovic Courtès [this message]
2018-12-14 15:20 ` Pierre Neidhardt
2018-12-15 18:10 ` Ludovic Courtès
2018-12-15 18:19 ` Pierre Neidhardt
2018-12-15 19:52 ` Leo Famulari
2018-12-15 19:57 ` Pierre Neidhardt
2018-12-15 19:55 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wooc17pw.fsf@gnu.org \
--to=ludo@gnu.org \
--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 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.