From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix Data Service - September update
Date: Wed, 02 Oct 2019 09:05:29 +0100 [thread overview]
Message-ID: <87d0ffpo6u.fsf@cbaines.net> (raw)
In-Reply-To: <871rwmr2yk.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> That would be great. In the end, it seems to be that there are quite a
> few services we could build around the Data Service. I’m not sure how
> they should interact.
>
> For instance, Mumi could talk to data.guix.gnu.org over an HTTP API, or
> should we replicate the database at issues.guix.gnu.org so that Mumi can
> tap directly into it?
>
> Likewise, how should something like hpcguix-web (the package browser at
> <https://hpc.guix.info/browse>) exploit available data, for instance to
> show the history of package versions?
So I've got an initial thing working for the version histories now. You
can construct a URL like [1], which will show a table about the known
versions of the package (icecat in this case) on the master branch.
1: http://data.guix.gnu.org/repository/1/branch/master/package/icecat
The same data is available in JSON [2], and that might work for getting
the data in the hpcguix-web service.
2: http://data.guix.gnu.org/repository/1/branch/master/package/icecat.json
Fetching the data for individual packages definately won't work well for
all applications, so I'm definately open to exposing the data in other
ways as well.
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next prev parent reply other threads:[~2019-10-02 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 19:14 Guix Data Service - September update Christopher Baines
2019-09-11 20:29 ` Ludovic Courtès
2019-09-14 10:51 ` Christopher Baines
2019-09-16 15:10 ` zimoun
2019-10-02 8:05 ` Christopher Baines [this message]
2019-10-02 10:49 ` Alex Sassmannshausen
2019-10-06 9:52 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0ffpo6u.fsf@cbaines.net \
--to=mail@cbaines.net \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.