On Wed, Nov 27, 2019 at 02:43:48PM -0700, Chris Murphy wrote:
On Wed, Nov 27, 2019 at 12:18 PM Neal Gompa
<ngompa13(a)gmail.com> wrote:
...snip...
>
> I'd love to explore using Btrfs for doing it. I have no idea how to
> get started with that...
Before Btrfs specific, I'd ask how much compression configurability is
needed in the compose system and where? That relates to plain squashfs
images as well as hypothetical Btrfs images. Is there any advantage to
having Rawhide use zstd:3 since these nightlies are throw away? These
would be much faster to create and use than xz or zstd:16, but the ISO
size would be a lot bigger, maybe 25% bigger. And then for branched
nightlies, RCs, and releases, use zstd:16 or even zstd:19? Could the
granularity be compress=low,medium,high? And that is then translated
by lmc or even the installer, into the specific level numbers? This is
in effect the question I'm posing here:
https://pagure.io/releng/issue/8581#comment-613760
I think we should just use the same everywhere, or we risk testing
something that is not actually what we ship.
I also don't think we should tie this work to btrfs.
If it also works there, great, but requiring that would be moving us to
btrfs by default, which we have not done.
kevin