From: zimoun <zimon.toutoune@gmail.com>
To: "Todor Kondić" <tk.code@protonmail.com>,
"help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: Re: guix pack and exposing ports
Date: Fri, 20 Aug 2021 10:20:38 +0200 [thread overview]
Message-ID: <86eeaoplwp.fsf@gmail.com> (raw)
In-Reply-To: <4no0564iP4u1kbR3RQCYehUZKZl5ijwMQZqXrwP9MevWQE1Hh6fayNOPVIIXlSJ4cHZ2bd8NFstJgp8RIEIyRWpzjumzWbUKjQDMO4dXjcw=@protonmail.com>
Hi,
In addition to Edouard’s answer. ;-)
On Wed, 18 Aug 2021 at 21:00, Todor Kondić <tk.code@protonmail.com> wrote:
> Also, I note I'm getting ~10 GiG image for a flimsy program depending
> on R and shiny. Somehow that doesn't feel right. :)
Well, it is a complicated topic. ;-) One thing is to carefully examine
the graph and then identify unnecessary (potentially) dependencies,
i.e., somehow create variant packages where the graph is drastically
cut. For instance, the package ’r-minimal’ brings TeXlive (mainly for
doc) and maybe it is not necessary for your use-case. You can use “guix
size” to identify the items.
On the other hand, “guix pack” can be optimized. For instance using
Docker layers, see:
<https://storage.googleapis.com/nixdoc/nixery-layers.html>
Chris did some work in this direction, IIRC. Maybe a patch is floating
around. :-)
All the best,
simon
prev parent reply other threads:[~2021-08-20 8:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 21:00 guix pack and exposing ports Todor Kondić
2021-08-19 9:40 ` Edouard Klein
2021-08-19 9:54 ` Todor Kondić
2021-08-20 8:20 ` zimoun [this message]
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=86eeaoplwp.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=tk.code@protonmail.com \
/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).