From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Medium-term road map
Date: Sun, 03 May 2020 22:07:50 +0200 [thread overview]
Message-ID: <87a72oye7d.fsf@gnu.org> (raw)
In-Reply-To: <875zdmnm6q.fsf@cbaines.net> (Christopher Baines's message of "Sun, 26 Apr 2020 19:20:29 +0100")
Hey!
Christopher Baines <mail@cbaines.net> skribis:
> zimoun <zimon.toutoune@gmail.com> writes:
>
>> 2. Search on all the packages included in Guix since the Big Bang.
>>
>> It is difficult to find the Guix commit where one package goes in and
>> the commit where it goes out. The Guix Data Service (GDS) helps a lot
>> for that! But AFAIK, it is not possible from the CLI and I do not find
>> it handy when I need it (just because I need to open a webbrowser,
>> etc.).
>>
>> IMHO, there is 3 questions:
>> - how to build such full historical index locally? Even if it is expensive
>> - how to fetch it from GDS? Or any other substitue?
>
> It's far from "the Big Bang", but the data.guix.gnu.org instance of the
> Guix Data Service has data going back to the start of 2019, with some
> big gaps that are still being filled in. Once that's happened, it'll be
> feasible to start looking at going further back.
>
> On your point about fetching data, the Guix Data Service can return data
> in JSON, and it's been mentioned that there could be something like the
> (guix ci) module, but to access the Guix Data Service. Once the data is
> available, it would at least be feasible to use that for a command line
> interface.
Yup, that’s the most practical approach.
We could write a program to build a database locally (I very much like
the idea of “substitutes” viewed as an optimization compared to local
computation) but that would be expensive, although it could be
incremental.
I suppose we could reuse relevant bits of the Data Service as a library.
Hmm thinking about it, by building the package-cache derivation of each
Guix revision, one already gets a lot of information, and that is
substitutable. Food for thought!
Ludo’.
next prev parent reply other threads:[~2020-05-03 20:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 13:37 Medium-term road map Ludovic Courtès
2020-04-25 16:23 ` Pierre Neidhardt
2020-05-03 20:13 ` Ludovic Courtès
2020-04-25 21:38 ` Jack Hill
2020-04-26 1:22 ` Josh Marshall
2020-05-03 20:18 ` Ludovic Courtès
2020-05-06 17:03 ` [EXT] " Thompson, David
2020-05-06 18:58 ` Efraim Flashner
2020-05-06 19:46 ` Jack Hill
2020-05-07 12:24 ` [EXT] " Thompson, David
2020-04-26 16:06 ` zimoun
2020-04-26 18:20 ` Christopher Baines
2020-05-03 20:07 ` Ludovic Courtès [this message]
2020-05-04 10:32 ` zimoun
2020-04-26 18:14 ` Christopher Baines
2020-05-03 20:11 ` Ludovic Courtès
2020-04-27 8:16 ` Andy Wingo
2020-04-27 13:06 ` Christopher Lemmer Webber
2020-04-30 21:27 ` Joshua Branson
2020-05-05 23:50 ` raingloom
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=87a72oye7d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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).