From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Per-package compression
Date: Fri, 28 Feb 2020 11:34:41 +0100 [thread overview]
Message-ID: <20200228103441.CJQrhi0rH3TJ2TqrJQxyGX_WuN9MIw29oVO0h9vNITg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19386@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1594 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/19386#issuecomment-592453465
Comment:
We could use this if we don't want to break compatibility for now.
But I think in general it is good to have the option to choose a better compression for specific (large packages), maybe even extend it to allow patterns for packages that need better compression.
I think there are a few candidates where where we could optimize for size instead of speed:
```
0ad-data-0.0.23b_1: 1996MB (https://alpha.de.repo.voidlinux.org/current)
linux3.18-dbg-3.18.124_1: 2207MB (https://alpha.de.repo.voidlinux.org/current/debug)
linux3.16-dbg-3.16.82_1: 2250MB (https://alpha.de.repo.voidlinux.org/current/debug)
flightgear-data-2019.1.1_1: 2504MB (https://alpha.de.repo.voidlinux.org/current)
linux4.4-dbg-4.4.213_1: 2579MB (https://alpha.de.repo.voidlinux.org/current/debug)
linux4.9-dbg-4.9.213_1: 3127MB (https://alpha.de.repo.voidlinux.org/current/debug)
linux4.14-dbg-4.14.170_1: 3411MB (https://alpha.de.repo.voidlinux.org/current/debug)
linux4.19-dbg-4.19.106_1: 3644MB (https://alpha.de.repo.voidlinux.org/current/debug)
linux5.2-dbg-5.2.21_1: 3833MB (https://alpha.de.repo.voidlinux.org/current/debug)
linux5.3-dbg-5.3.18_1: 3968MB (https://alpha.de.repo.voidlinux.org/current/debug)
linux5.4-dbg-5.4.22_1: 4006MB (https://alpha.de.repo.voidlinux.org/current/debug)
linux5.5-dbg-5.5.6_2: 4114MB (https://alpha.de.repo.voidlinux.org/current/debug)
kicad-packages3D-5.1.5_1: 4992MB (https://alpha.de.repo.voidlinux.org/current)
```
next prev parent reply other threads:[~2020-02-28 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19386@inbox.vuxu.org>
2020-02-28 9:03 ` xtraeme
2020-02-28 10:34 ` Duncaen [this message]
2020-02-28 11:03 ` xtraeme
2020-03-09 20:55 ` Chocimier
2020-03-09 20:56 ` [PR PATCH] [Closed]: " Chocimier
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=20200228103441.CJQrhi0rH3TJ2TqrJQxyGX_WuN9MIw29oVO0h9vNITg@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).