From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, Guile Devel <guile-devel@gnu.org>
Subject: Re: The size of ‘.go’ files
Date: Sat, 06 Jun 2020 14:21:09 -0500 [thread overview]
Message-ID: <878sh00zmi.fsf@gmail.com> (raw)
In-Reply-To: <87r1usli5f.fsf@gnu.org> (Mathieu Othacehe's message of "Sat, 06 Jun 2020 10:20:44 +0200")
Mathieu Othacehe <othacehe@gnu.org> writes:
> Having a lighter disk-image isn't very important on desktop, but for the
> embedded devices with small eMMC, any improvement would be really
> welcome :)
I was recently discussing a Guix buildbox container image I put together
with a coworker, and one of the tremendous downsides was the size of the
image. I think smaller images are important all around! I'm looking
forward to seeing your work.
--
Katherine
next prev parent reply other threads:[~2020-06-06 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 20:50 The size of ‘.go’ files Ludovic Courtès
2020-06-06 8:20 ` Mathieu Othacehe
2020-06-06 19:21 ` Katherine Cox-Buday [this message]
2020-06-07 9:07 ` Pierre Neidhardt
2020-06-08 8:07 ` Andy Wingo
2020-06-09 16:09 ` Ludovic Courtès
2020-06-24 12:11 ` Andy Wingo
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878sh00zmi.fsf@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=othacehe@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.
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).