From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org, guix-science@gnu.org,
zimoun <zimon.toutoune@gmail.com>
Subject: Re: Software Heritage fifth anniversary event
Date: Thu, 02 Dec 2021 09:59:18 +0100 [thread overview]
Message-ID: <87k0gnxtzt.fsf@inria.fr> (raw)
In-Reply-To: <87tufsgq1p.fsf@ngyro.com> (Timothy Sample's message of "Wed, 01 Dec 2021 13:04:18 -0500")
Hi!
Timothy Sample <samplet@ngyro.com> skribis:
> Ludovic Courtès <ludovic.courtes@inria.fr> writes:
[...]
>> • Disarchive: they’d like to better understand the “unknowns” in the
>> PoG plots (I wasn’t sure if it was non-tar.gz tarballs or what) and
>> to work on the definitely-missing origins that show up there;
>
> Many of the unknowns are there for me to track Disarchive progress.
> It’s not really the clearest reporting, but it tracks more what Guix can
> handle automatically than what we could theoretically know about.
> Basically something is “known” if it can be downloaded from upstream,
> and either: it’s a non-recursive Git reference; or it’s something
> Disarchive can handle. Hence, we know nothing about other version
> control systems and, say, “.tar.bz2” archives. Also, all these things
> are based on heuristics. :) As we get closer to 100% known, we can
> start analyzing everything more closely.
Right. Perhaps at some point we can give them (say on swh-devel) this
explanation so they have a clearer view of how far Disarchive is from
being “production-ready” from an SWH perspective. Valentin of the SWH
team played a lot with pristine-tar and I’m sure they’d have useful
feedback to give.
>> they’re not opposed to the idea of eventually hosting or maintaining
>> the Disarchive database (in fact one of the developers thought we
>> were hosting it in Git and that as such they were already archiving
>> it—maybe we could go back to Git?);
>
> It’s a possibility, but right now I’m hopeful that the database will be
> in the care of SWH directly before too long. I’d rather wait and see at
> this point. I’m sure we could manage it, but the uncompressed size of
> the Disarchive specification of a Chromium tarball is 366M. Storing all
> the XZ specifications uncompressed is over 20G. It would be a big Git
> repo!
Indeed!
So, in passing, you’re telling us that xz support is kinda ready, right?
:-)
Thanks!
Ludo’.
next prev parent reply other threads:[~2021-12-02 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 9:41 Software Heritage fifth anniversary event Ludovic Courtès
2021-12-01 18:04 ` Timothy Sample
2021-12-02 8:59 ` Ludovic Courtès [this message]
2021-12-02 13:17 ` zimoun
2021-12-02 14:04 ` Timothy Sample
2021-12-02 15:49 ` zimoun
2021-12-02 18:04 ` Ludovic Courtès
2021-12-02 15:02 ` Ludovic Courtès
2021-12-03 3:58 ` Maxim Cournoyer
2021-12-03 11:01 ` Ludovic Courtès
2021-12-05 5:10 ` Maxim Cournoyer
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=87k0gnxtzt.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-devel@gnu.org \
--cc=guix-science@gnu.org \
--cc=samplet@ngyro.com \
--cc=zimon.toutoune@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).