From: Mathieu Othacehe <m.othacehe@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 39941@debbugs.gnu.org
Subject: bug#39941: Disk-image size increase on core-updates.
Date: Thu, 12 Mar 2020 09:06:29 +0100 [thread overview]
Message-ID: <87wo7qyp2y.fsf@gmail.com> (raw)
In-Reply-To: <87r1xyfx7o.fsf@gnu.org>
Hi,
> 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!
Ok then, I'll give it a try.
> 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.
Yep, it would be very helpful to track package closure size and
cross-compilation status using the CI. When sending a patch to Linux,
you get emails that inform you that you may have broken the build for a
specific architecture, in a specific configuration.
We would really need this kind of feedback for cross-compilation as very
few people actually use it, and it is really easy to break it. That's
something I'd like to discuss with Chris soon.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-03-12 8:07 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
2020-03-12 8:06 ` Mathieu Othacehe [this message]
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=87wo7qyp2y.fsf@gmail.com \
--to=m.othacehe@gmail.com \
--cc=39941@debbugs.gnu.org \
--cc=ludo@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).