From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org,
Francesco Riosa <vivo75@gmail.com>,
Brian Dolbec <dolsen@gentoo.org>
Subject: Re: [gentoo-portage-dev] [PATCH] Default BINPKG_COMPRESSION to zstd (bug 715108)
Date: Mon, 25 May 2020 21:49:33 -0700 [thread overview]
Message-ID: <2b7e05f6-bf00-8b0a-3fc3-f68c1e024e8e@gentoo.org> (raw)
In-Reply-To: <05089945-53fa-b065-04d6-1ea631a4bee2@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 873 bytes --]
On 5/12/20 1:28 AM, Francesco Riosa wrote:
>
> Il 11/05/20 22:21, Brian Dolbec ha scritto:
>> On Sun, 10 May 2020 19:29:34 -0700
>> Zac Medico <zmedico@gentoo.org> wrote:
>>
>>> This includes a _compat_upgrade.binpkg_compression script that the
>>> ebuild can call in pkg_preinst in order to maintain a
>>> backward-compatible bzip2 default when appropriate, ensuring that
>>> binary package consumers are not caught off guard.
>
> [snip]
>
> For your interest, the binpkg archive for a small LAMP container goes
> from 659 to 540 MB, the "--rm" flag isn't really needed for binpkgs but
> it help reminder that zstd is the only one that does _not_ remove the
> original file after compression
>
> BINPKG_COMPRESS="zstd"
> BINPKG_COMPRESS_FLAGS="--rm --long --threads=1 --adapt=min=7,max=19"
I'm using those flag now. Thanks!
--
Thanks,
Zac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2020-05-26 4:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 2:29 [gentoo-portage-dev] [PATCH] Default BINPKG_COMPRESSION to zstd (bug 715108) Zac Medico
2020-05-11 20:21 ` Brian Dolbec
2020-05-12 8:28 ` Francesco Riosa
2020-05-26 4:49 ` Zac Medico [this message]
2020-05-26 4:48 ` Zac Medico
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2b7e05f6-bf00-8b0a-3fc3-f68c1e024e8e@gentoo.org \
--to=zmedico@gentoo.org \
--cc=dolsen@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
--cc=vivo75@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox