From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 42019@debbugs.gnu.org, Christopher Baines <mail@cbaines.net>
Subject: [bug#42019] [PATCH 1/1] website: Add integrity to JSON sources.
Date: Tue, 30 Jun 2020 01:28:45 +0200 [thread overview]
Message-ID: <864kqtbgeq.fsf@gmail.com> (raw)
In-Reply-To: <87v9j9a9ko.fsf@gnu.org>
Hi Chris,
On Mon, 29 Jun 2020 at 22:41, Ludovic Courtès <ludo@gnu.org> wrote:
> zimoun <zimon.toutoune@gmail.com> skribis:
>
>> BTW, in the SWH picture and after a chat video with lewo, I do not
>> think that the website is the right place. Instead, it should go to
>> ci.guix.gnu.org or data.guix.gnu.org. Or maybe integrated with "guix
>> publish". Well, the next step is to have a collection of sources.json
>> -- that the point of "revision". WDYT?
>
> The Guix Data Service would be a natural place for ‘sources.json’ IMO.
> Thoughts, Chris?
If it goes to the GDS, then first let point me where to start. :-)
And second, it could be nice in the "near" future to have at least 2
sources.json: one for the last commit refreshed every X minutes (or
hours) and another one containing the concatenation of all the sources
of Guix (at least the one reachable by guix time-machine i.e. after the
big overhaul of Inferiors). I will go on #swh-devel or reach lewo to
know how "near" it is on SWH side.
Cheers,
simon
next prev parent reply other threads:[~2020-06-29 23:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 15:13 [bug#42019] [PATCH 0/1] sources.json compliant with SWH loader zimoun
2020-06-23 15:21 ` [bug#42019] [PATCH 1/1] website: Add integrity to JSON sources zimoun
2020-06-27 17:05 ` Ludovic Courtès
2020-06-27 17:41 ` zimoun
2020-06-29 17:01 ` zimoun
2020-06-29 20:41 ` Ludovic Courtès
2020-06-29 23:28 ` zimoun [this message]
2020-07-01 19:35 ` Christopher Baines
2020-07-01 20:29 ` zimoun
2020-06-29 16:50 ` [bug#42019] [PATCH v2] " zimoun
2020-07-06 10:20 ` bug#42019: " 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=864kqtbgeq.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=42019@debbugs.gnu.org \
--cc=ludo@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 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.