From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Othacehe Subject: bug#39941: Disk-image size increase on core-updates. Date: Thu, 12 Mar 2020 09:06:29 +0100 Message-ID: <87wo7qyp2y.fsf@gmail.com> References: <87sgimdjcj.fsf@gmail.com> <87eeu0h8d6.fsf@gmail.com> <87a74nhstf.fsf@gnu.org> <87zhcnympn.fsf@gmail.com> <87r1xyfx7o.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:42529) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jCIrv-0001PR-Ow for bug-guix@gnu.org; Thu, 12 Mar 2020 04:07:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jCIru-0005qC-KK for bug-guix@gnu.org; Thu, 12 Mar 2020 04:07:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:49897) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jCIru-0005q6-Gn for bug-guix@gnu.org; Thu, 12 Mar 2020 04:07:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jCIru-0005wK-BL for bug-guix@gnu.org; Thu, 12 Mar 2020 04:07:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87r1xyfx7o.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 39941@debbugs.gnu.org Hi, > Ah yes, we should try to introduce a =E2=80=9Clib=E2=80=9D output there a= s well. I > vaguely remember this was tricky but I=E2=80=99m not sure why; worth a tr= y! 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-gui= le-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=E2=80= =99m > 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