From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Baines Subject: Re: Package file indexing Date: Thu, 02 Jan 2020 19:15:41 +0000 Message-ID: <87png11xgi.fsf@cbaines.net> References: <20190314204941.GA21065@jasmine.lan> <87mulx9kuv.fsf@nckx> <87zhpx846u.fsf@ambrevar.xyz> <87bm21y2s2.fsf_-_@gnu.org> <87imw7cpe7.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> <87pnqdhkpf.fsf@gnu.org> <87imlt3hr2.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:50860) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1in5wj-0006xc-IU for guix-devel@gnu.org; Thu, 02 Jan 2020 14:15:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1in5wi-0006gB-Bj for guix-devel@gnu.org; Thu, 02 Jan 2020 14:15:49 -0500 Received: from mira.cbaines.net ([2a01:7e00::f03c:91ff:fe69:8da9]:38472) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1in5wi-0006eH-3Y for guix-devel@gnu.org; Thu, 02 Jan 2020 14:15:48 -0500 In-reply-to: <87imlt3hr2.fsf@ambrevar.xyz> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Pierre Neidhardt writes: > Hello again! > > I'm resurrecting this since I've just started working on this as part of > the NGI application! :) > >>>> Internally it=E2=80=99d call =E2=80=98guix substitute=E2=80=99 to fetc= h the file index from >>>> the substitute server, check its signature, cache it locally, and then >>>> look up the file. > > What about storing the file listing in the narinfo instead? > Is this doable? If so, then it should be quite simple to implement, it > would basically mimic "guix size." I haven't followed this thread particularly well, but at least from my recent experience messing with nar and narinfo stuff in the Guix Data Service, I'd be cautious about trying to adapt narinfo files for this purpose. It seems to me that the narinfo file is a good at capturing the information about the hash, size, location and signature of the nar. They're small, and human readable. I think making information about the contents of Guix store items more available is great, but even in the average case, it seems like that's too much information to pack in to a narinfo file. Imagining a manifest in abstract, having a list of the files and directories as well as the hashes and sizes of the files could be really useful, but that for most store items, all that information is much larger than the narinfo files. A separate file might be more flexible. Additionally, now that I'm thinking about this, having information about each store item is great, but if you want to know which store items in a particular revision of Guix contain files called foo, then it might take a while to download and search them all. Having something that's focused around the packages in a channel, and acts as an index for all of the files in all of the available outputs might be faster to search, by doing the combining of the data upfront. Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAl4OQV1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9XdVTQ/5AaUiS/TPzJYQuTXii5P7P5CmlVz+AKOxSHSGYij4GLUtAKZw6bVO3Doh 7tcsm+Zjokz2mYl/Jo1e9/XJFEX64Wk3w2YnlD9dEy2RHchmaDjlTFuECcizvW+g hxkJFGfufIZlr53afQG2so0F16V2O4va282qURShhS/2IqNOD3YwoBxCfTDYNM2R I4WTuWqiRC2pyzM0V0REM3h0nA8lkCjRL86LsdJgSIMuKMkCd12qL073soduGuO1 vnYp1jO68BXI5AG6RrZdBroGqDQXo/qmjxPqqenK8kze4EJR06AD1ruPvOcQbG2M B/LESe69jZ46YAsWr6OSWjJLOk/qhlRegswZBk12rPOkDEFM6jJ0MgwtYx8W1Cqv cuUEtV1xETf/IIWYjkcetZGSYn8egJ1th/4pefV4Gb8ZwlgzPh0xXUvigA+dZMz0 PWburKhuFk6REEbih/dKazpB3od86mQiB4bEb4LoJxwd5xC2dfhDsDfVSqvcjOdW jAAkQaHwY+L5CE6ykkIElbgTcfcSl4Fnq1Cfgfx0vCJJWUvavdQqAJI8RYpb8w1+ lAKLZ2nIyURL8pNO8oeO6X585D9H70kp+WD2t3OAsfowOjsJfDgkZr3Fq4FRAUpn DMl3jRbzUrn+nEecg3mhAhoAhycRb2t0TZIJwoKlKnmAkNAOkE4= =fRqw -----END PGP SIGNATURE----- --=-=-=--