unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 39941@debbugs.gnu.org
Subject: bug#39941: Disk-image size increase on core-updates.
Date: Wed, 11 Mar 2020 21:33:31 +0100	[thread overview]
Message-ID: <87r1xyfx7o.fsf@gnu.org> (raw)
In-Reply-To: <87zhcnympn.fsf@gmail.com> (Mathieu Othacehe's message of "Wed, 11 Mar 2020 15:45:24 +0100")

Hi!

Mathieu Othacehe <m.othacehe@gmail.com> skribis:

> Turns out on master,
>
> guix size `guix build guile|grep -v debug`
>
>
> returns ~124 MiB, while,
>
> guix size `guix build --target=aarch64-linux-gnu guile|grep -v debug`
>
> returns ~523 MiB.
>
> When building the native guile, only the "lib" output of gcc is
> kept. When cross-compiling, the whole cross-compiler is dragged down (as
> there's only "out" defined for cross-gcc).

Ah yes, we should try to introduce a “lib” output there as well.  I
vaguely remember this was tricky but I’m not sure why; worth a try!

> That does not explain the sudden increase, but this is still quite
> unfortunate :p

Yep, would also be nice to track down.

Speaking of which, the Data Service has things like:

  http://data.guix.gnu.org/gnu/store/p8in2npgl5yhliy25ikz7shjbq0gii95-guile-next-3.0.0

We could eventually use it to track the evolution of the size of
individual packages, or that of their closure (even for cross-compiled
packages).  I remember a discussion with Chris Baines on this but I’m
not sure what the outcome was.

Ludo’.

  reply	other threads:[~2020-03-11 20:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06  7:37 bug#39941: Disk-image size increase on core-updates Mathieu Othacehe
2020-03-10  9:22 ` Mathieu Othacehe
2020-03-11 14:25   ` Ludovic Courtès
2020-03-11 14:45     ` Mathieu Othacehe
2020-03-11 20:33       ` Ludovic Courtès [this message]
2020-03-12  8:06         ` Mathieu Othacehe
2020-03-14 10:54         ` Mathieu Othacehe
2020-03-14 12:30           ` Marius Bakke
2020-03-15 11:21             ` Mathieu Othacehe
2020-03-15 17:13               ` Ludovic Courtès
2020-03-17 11:28                 ` Mathieu Othacehe
2020-03-24 10:54                   ` Ludovic Courtès
2020-03-24 17:01                     ` Mathieu Othacehe
2020-03-25 21:34                       ` Ludovic Courtès

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=87r1xyfx7o.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39941@debbugs.gnu.org \
    --cc=m.othacehe@gmail.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. 
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).