From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] linux-firmware: Compress firmware on disk
Date: Thu, 24 Mar 2022 10:55:07 +0000
Message-ID: <38a58e63-69ab-f901-b171-4f7e5358347b@ipfire.org>
In-Reply-To: <213CD0DA-9253-43AB-AEE2-907E24324A18@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6877803082218918040=="
List-Id: <development.lists.ipfire.org>

--===============6877803082218918040==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Michael,

well, contrary to your expectation, shipping the compressed linux-firmware le=
ads to an way too big update:

$ cat ./install/packages/meta-core-upgrade-166
Name: core-upgrade
Summary: IPFire Core Update
ProgVersion: 2.27
Release: 166
Size: 299315200
Dependencies:=20
File: core-upgrade-2.27-166.ipfire
Services:=20
$ ls -lah ./install/packages/core-upgrade-2.27-166.ipfire
-rw-r--r-- 1 root root 286M 24. Mar 10:43 ./install/packages/core-upgrade-2.2=
7-166.ipfire

I do not have the figure ready how much of that 286 MByte are caused by linux=
-firmware, but
it has to be way more than 100 MBytes. Otherwise, Core 166 would have been to=
 big already, which
I doubt when looking at the currently included filelists.

Thanks, and best regards,
Peter M=C3=BCller


> Hello,
>=20
> So Peter has merged this patch now and it has resulted in an increase of ab=
out 70M of the ISO image. This is expected since we are now compressing every=
thing individually which will give us a worse compression ratio.
>=20
> I assume that the updater would grow in a similar size which is probably ac=
ceptable to me.
>=20
> Since we suffer from bloated Core Updates, I wanted to double-check with ev=
erybody that this is okay for everybody else, too.
>=20
> Best,
> -Michael

--===============6877803082218918040==--