unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: 56030@debbugs.gnu.org
Subject: bug#56030: The guix pull profile is too big
Date: Fri, 17 Jun 2022 07:48:28 +0200	[thread overview]
Message-ID: <2C6CCC4B-BC71-4CA4-9B7B-086C14713DCD@lepiller.eu> (raw)

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

Hi Guix!

I figured out this morning that my guix pull profile ("current") was more than 1GB. Looking at the closure, I found a few oddities.

There's gcc in there, which is the second most important contributor after guix-*-modules (150 MB). It's referenced by gcc-toolchain, itself only referenced by the guile-wrapper we build in (guix self). Can we get rid of it?

There are three versions of guile (50 MB each). Can we settle for only one?

Then maybe less important because they're small:

There are two libffi, gzip, zlib, libgc, bash-minimal, xz, pkg-config and libunistring.

We have bash-minimal and bash-static. The latter is a bit bigger than the former. Maybe we can keep only bash-minimal?

[-- Attachment #2: Type: text/html, Size: 780 bytes --]

             reply	other threads:[~2022-06-17  5:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  5:48 Julien Lepiller [this message]
2022-06-26 21:20 ` bug#56030: The guix pull profile is too big Ludovic Courtès
2022-08-30 10:04   ` zimoun
2022-07-21 14:52 ` Maxime Devos
2022-07-21 15:03   ` paren--- via Bug reports for GNU Guix
2022-07-21 15:38     ` paren--- via Bug reports for GNU Guix
2022-08-06 23:37     ` bug#56030: rfc2822 permits that left paren, but why do it? -- was " bokr
2022-07-21 15:11   ` paren--- via Bug reports for GNU Guix
2022-07-21 15:42     ` Julien Lepiller
2022-07-21 15:48       ` paren--- via Bug reports for GNU Guix
2022-07-21 15:52         ` paren--- via Bug reports for GNU Guix
2022-07-21 15:46     ` Maxime Devos
2022-07-21 15:49       ` paren--- via Bug reports for GNU Guix
2022-07-21 15:52         ` Julien Lepiller
2022-07-21 15:53         ` Maxime Devos
2022-07-21 16:13   ` paren--- via Bug reports for GNU Guix
2022-07-21 16:22     ` Maxime Devos
2022-07-21 16:29       ` paren--- via Bug reports for GNU Guix
2022-07-21 16:35         ` Maxime Devos

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=2C6CCC4B-BC71-4CA4-9B7B-086C14713DCD@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=56030@debbugs.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).