From: Taylan Kammer <taylan.kammer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Guix Devel" <guix-devel@gnu.org>
Subject: Re: Identical files across subsequent package revisions
Date: Wed, 23 Dec 2020 10:08:27 +0100 [thread overview]
Message-ID: <9851ca1f-ae56-66f3-912c-55db3f053c80@gmail.com> (raw)
In-Reply-To: <87wnx9wlea.fsf@gnu.org>
On 22.12.2020 23:01, Ludovic Courtès wrote:
>
> Thoughts? :-)
>
My first thought: Neat, would love to see this implemented! :D
My second thought: it's surprising that IceCat supposedly changes so
much between releases. I suppose the reason is that this analysis is on
a per-file basis, and IceCat is mostly a massive binary. That leads me
to wonder: what about binary diffs for large files?
Perhaps for all files that are bigger than N bytes, we could check if
the binary diff is X% or smaller of the total size, and if so, the build
servers could host the diff file alongside the full file. (Substitute N
and X for sensible values, like maybe 5 MB and 50%.)
But that could be a second, separate step I suppose.
- Taylan
next prev parent reply other threads:[~2020-12-23 9:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 22:01 Identical files across subsequent package revisions Ludovic Courtès
2020-12-23 9:08 ` Taylan Kammer [this message]
2020-12-23 10:50 ` Pierre Neidhardt
2020-12-23 22:06 ` Mark H Weaver
2020-12-23 22:47 ` Jonathan Brielmaier
2020-12-23 23:42 ` Mark H Weaver
2020-12-23 10:19 ` zimoun
2020-12-23 10:41 ` zimoun
2020-12-27 22:22 ` Ludovic Courtès
2020-12-23 11:48 ` Christopher Baines
2020-12-23 13:10 ` Miguel Ángel Arruga Vivas
2020-12-23 14:07 ` zimoun
2020-12-23 15:40 ` Julien Lepiller
2020-12-23 19:07 ` Miguel Ángel Arruga Vivas
2020-12-27 22:29 ` Ludovic Courtès
2021-01-06 9:39 ` Ludovic Courtès
2020-12-29 20:01 ` pukkamustard
2021-01-06 9:27 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9851ca1f-ae56-66f3-912c-55db3f053c80@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).