From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julien Lepiller <julien@lepiller.eu>
Subject: Re: Guix size reduction work group
Date: Tue, 04 Feb 2020 12:59:05 -0500
Message-ID: <5224E885-3C5C-4EA7-BC57-179EA55A8181@lepiller.eu>
References: <87pneul50i.fsf@ambrevar.xyz>
 <CAJ3okZ2mLhGEGU5TMnuhtsd-M2T88DzyXbbatWmPiRAhQQGCRw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:56412)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <julien@lepiller.eu>) id 1iz2Tv-0004c2-GS
 for guix-devel@gnu.org; Tue, 04 Feb 2020 12:59:28 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <julien@lepiller.eu>) id 1iz2Tt-0007qz-QW
 for guix-devel@gnu.org; Tue, 04 Feb 2020 12:59:27 -0500
In-Reply-To: <CAJ3okZ2mLhGEGU5TMnuhtsd-M2T88DzyXbbatWmPiRAhQQGCRw@mail.gmail.com>
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org
Sender: "Guix-devel"
 <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>, Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>

Le 4 f=C3=A9vrier 2020 11:22:10 GMT-05:00, zimoun <zimon=2Etoutoune@gmail=
=2Ecom> a =C3=A9crit :
>Hi Pierre,
>
>On Tue, 4 Feb 2020 at 16:57, Pierre Neidhardt <mail@ambrevar=2Exyz>
>wrote:
>
>> Shall we start a work group to fix the issue?
>
>One of the obvious bottleneck is the documentation=2E Some packages come
>with a full doc and sometimes with Pandoc and/or TeX stuff=2E In
>general, it is required but when speaking about more minimalism=2E=2E=2E
>So, the only way is to examine package by package and to check the
>status of the documentation, IMHO=2E
>
>
>All the best,
>simon

Another thing to address is the package closure size by pruning some eleme=
nts from packages' closures=2E The obvious one is gcc, that appears in some=
 closure because of a file that registers compilation commands for instance=
=2E Another situation is when a package requires a part of another package,=
 and another part of that package (unused) requires more stuff=2E
This happened with mariadb: some software needed mariadb's library, but th=
e mariadb also came with binaries that required more dependencies=2E Splitt=
ing mariadb reduced the closure of qt5 by 200 MB for instance, for a combin=
ation of these two reasons, and the fact that binaries in mariadb are reall=
y big=2E