From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Julien Lepiller <julien@lepiller.eu>,
help-guix@gnu.org, Marius Bakke <mbakke@fastmail.com>
Cc: Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: Guix closure size of a system?
Date: Tue, 19 May 2020 14:50:39 +0200 [thread overview]
Message-ID: <87wo58gkbk.fsf@ambrevar.xyz> (raw)
In-Reply-To: <B6509EF7-3BD3-43E5-806B-EA51C166FAF0@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
Julien Lepiller <julien@lepiller.eu> writes:
>>Moving the llvm libs to a "lib" output could reduce the closure size of
>>many packages I believe.
>>
>>Thoughts?
>
> Llvm doesn't support that afaik.
Does not support what?
Arch Linux has a separate llvm-libs package, I suppose we can do
something similar.
> I've recently found that we have a 30MB static library in mozjs (a gdm dependency) that is described as unused by other packages in FS, and they suggest to remove it.
>
> Another easy win is the 30MB gnome-backgrounds which useless on my system, as I don't use gnome. Not sure why it's in the closure of gdm.
>
> We could gain 50MB in the closure of many software (but not the system) by placing gnutls guile bindings in their own output (for instance, icecat depends on ffmpeg which depends on gnutls which in turn depends on guile). This might still be useful to reduce the size of separate profiles.
>
> I'll probably send a some patches in the next few days :)
Fantastic, and thankgs for your insights!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-05-19 12:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 6:19 Guix closure size of a system? Pierre Neidhardt
2020-05-19 6:30 ` Mathieu Othacehe
2020-05-19 7:15 ` Pierre Neidhardt
2020-05-19 9:33 ` Marius Bakke
2020-05-19 9:57 ` Pierre Neidhardt
2020-05-19 12:21 ` Julien Lepiller
2020-05-19 12:50 ` Pierre Neidhardt [this message]
2020-05-19 13:05 ` Julien Lepiller
2020-05-19 15:41 ` Leo Famulari
2020-05-19 15:58 ` Pierre Neidhardt
2020-05-19 16:22 ` Leo Famulari
2020-05-19 16:46 ` Pierre Neidhardt
2020-05-19 17:28 ` Leo Famulari
2020-05-19 10:52 ` Tobias Geerinckx-Rice
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=87wo58gkbk.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=mbakke@fastmail.com \
--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).