GNU bug report logs - #39941
Disk-image size increase on core-updates.

Previous Next

Package: guix;

Reported by: Mathieu Othacehe <m.othacehe <at> gmail.com>

Date: Fri, 6 Mar 2020 07:38:01 UTC

Severity: normal

Done: Mathieu Othacehe <mathieu <at> cervin.i-did-not-set--mail-host-address--so-tickle-me>

Bug is archived. No further changes may be made.

Full log


Message #17 received at 39941 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 39941 <at> debbugs.gnu.org
Subject: Re: bug#39941: Disk-image size increase on core-updates.
Date: Wed, 11 Mar 2020 21:33:31 +0100
Hi!

Mathieu Othacehe <m.othacehe <at> 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’.




This bug report was last modified 4 years and 356 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.