Ludovic Courtès writes: > Christopher Baines 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 :)