From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Support returning build information by output.
Date: Thu, 16 Jan 2020 08:36:23 +0000 [thread overview]
Message-ID: <875zhbdchk.fsf@cbaines.net> (raw)
In-Reply-To: <87blrdej9s.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Christopher Baines <mail@cbaines.net> skribis:
>
>> Being able to take a derivation and query the build information is useful, but
>> in cases where there are multiple derivations that produce the same outputs,
>> the probability of getting the data back from Cuirass is reduced.
>>
>> This is because Cuirass might not have build the exact derivation you have,
>> but a different derivation that produces the same outputs (this can commonly
>> happen when a related fixed output derivation changes).
>>
>> Cuirass doesn't store derivations if they produce the same outputs as a
>> derivation it already knows about, so it can't determine if this is the
>> case. Therefore, provide a way of querying build results by output, rather
>> than derivation.
>>
>> The motivation behind this is to make it easier to import build information in
>> to the Guix Data Service.
>>
>> * src/cuirass/database.scm (db-get-output): New procedure.
>> * src/cuirass/http.scm (respond-output-not-found): New procedure.
>> (request-path-components): Handle /output/… requests.
>> * doc/cuirass.texi (Build information): Mention that you can get build
>> information by output.
>
> LGTM, thanks!
Great, I've pushed this now :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
prev parent reply other threads:[~2020-01-16 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 9:51 [PATCH] Support returning build information by output Christopher Baines
2020-01-08 21:21 ` Ludovic Courtès
2020-01-16 8:36 ` Christopher Baines [this message]
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=875zhbdchk.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.