From: Christopher Baines <mail@cbaines.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Another update on the Guix Data Service
Date: Thu, 09 Jan 2020 16:59:06 +0000 [thread overview]
Message-ID: <87a76w1s85.fsf@cbaines.net> (raw)
In-Reply-To: <87a76wanvk.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> writes:
>> Channel news entries are recorded in the database, you can see all that
>> are present in a revision [3], but the comparison page should show new
>> news entries as well.
>>
>> 3: http://data.guix.gnu.org/revision/06c8e87224decebc0a3d5bdc7d2ca13cb2b08299/news
>
> Is there a link to the news page from
>
> http://data.guix.gnu.org/revision/06c8e87224decebc0a3d5bdc7d2ca13cb2b08299
>
> ?
No, but there probably should be one.
>> - Automated code review for Guix patches, which I was working on when I
>> started working on the Guix Data Service, and most of the
>> functionality can be beneficial there.
>
> Some time ago you did some work on Patchwork.
>
> https://patchwork.cbaines.net/project/guix-patches/list/
>
> I haven't followed very closely, so I wonder what your plans are
> regarding patchwork and Guix Data Service.
So I'd like to resurrect my slightly clunky but somewhat working
Patchwork + Laminar + Git repo + Guix Data Service (+ Cuirass?) setup
for testing patches.
Here, the Guix Data Service would process the Guix revision with the
patches under test having been applied. This would reveal the lint
warning changes. It would also reveal the new derivations, which can be
built to check what the effect of the patches are.
> Last, is there any documentation on how to _use_ it? (I don't mean the setup.)
So the only documentation currently is the README file, which is
available at http://data.guix.gnu.org/README . I haven't considered
writing standalone documentation yet, but I have been considering
incorporating more in to the web interface.
Is there a specific thing you're interested in/unsure about?
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next prev parent reply other threads:[~2020-01-09 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 20:15 Another update on the Guix Data Service Christopher Baines
2020-01-09 11:08 ` Pierre Neidhardt
2020-01-09 16:59 ` Christopher Baines [this message]
2020-01-10 12:17 ` Pierre Neidhardt
2020-01-10 13:46 ` Christopher Baines
2020-02-05 10:20 ` Ludovic Courtès
2020-02-05 17:58 ` Christopher Baines
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=87a76w1s85.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).