From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: Preservation of Guix report 2022-01-16
Date: Tue, 18 Jan 2022 16:28:02 +0100 [thread overview]
Message-ID: <874k61f4hp.fsf@gnu.org> (raw)
In-Reply-To: <87y23fwjb8.fsf@ngyro.com> (Timothy Sample's message of "Sun, 16 Jan 2022 14:51:23 -0500")
Hi,
Timothy Sample <samplet@ngyro.com> skribis:
> I’ve published a new preservation of Guix report:
>
> https://ngyro.com/pog-reports/latest/
>
> Actually, the URL is <https://ngyro.com/pog-reports/2022-01-16/>, but I
> thought having a way to reference the latest report would be helpful.
Nice!
[...]
> A really important thing to do at this point is to verify that some
> reasonable looking computation is covered by what we are doing already.
> For instance, is every source used to build Guile (or Python or R)
> preserved? This will ensure that key sources are not missing, which is
> a real possibility given that everything so far has been purely a
> numbers game!
I wonder if we could have something similar to ‘guix weather -c’, which
would highlight missing sources with many dependents.
TeX Live is a big concern: it’s all Subversion, and everything depends
on those packages. IIRC, SWH does not support Subversion yet; and when
it does, we’ll have to adjust our code so it can actually fetch
Subversion checkouts from SWH. One issue is partial checkouts: all
these ‘texlive-’ packages refer to partial checkouts of the big TeX Live
repo.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2022-01-18 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 19:51 Preservation of Guix report 2022-01-16 Timothy Sample
2022-01-18 15:28 ` Ludovic Courtès [this message]
2022-01-18 18:16 ` Vagrant Cascadian
2022-01-18 19:38 ` Timothy Sample
2022-01-19 10:44 ` Ludovic Courtès
2022-01-20 9:35 ` zimoun
2022-01-24 15:17 ` 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=874k61f4hp.fsf@gnu.org \
--to=ludovic.courtes@inria.fr \
--cc=guix-devel@gnu.org \
--cc=samplet@ngyro.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.
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).