From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id o5PKFJAahl8bdAAA0tVLHw (envelope-from ) for ; Tue, 13 Oct 2020 21:22:24 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id qKc7EJAahl9fCgAAbx9fmQ (envelope-from ) for ; Tue, 13 Oct 2020 21:22:24 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 10E1E940414 for ; Tue, 13 Oct 2020 21:22:24 +0000 (UTC) Received: from localhost ([::1]:39834 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kSRkU-0007ay-WA for larch@yhetil.org; Tue, 13 Oct 2020 17:22:23 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:40928) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kSRkK-0007ak-BS for guix-devel@gnu.org; Tue, 13 Oct 2020 17:22:12 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:44424) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kSRkJ-0007CY-HC; Tue, 13 Oct 2020 17:22:11 -0400 Received: from [2a01:e0a:1d:7270:af76:b9b:ca24:c465] (port=59592 helo=ribbon) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kSRkI-0002bB-Pv; Tue, 13 Oct 2020 17:22:11 -0400 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= To: Pierre Neidhardt Subject: Re: File search progress: database review and question on triggers References: <87sgcuh8rb.fsf@ambrevar.xyz> <86imd4e7cr.fsf@gmail.com> <87eenspcf8.fsf@ambrevar.xyz> <865z94dz83.fsf@gmail.com> <87zh6gns4l.fsf@ambrevar.xyz> <87zh5c7hx6.fsf@ambrevar.xyz> <87k0w4zw8q.fsf@gnu.org> <875z7oijxu.fsf@ambrevar.xyz> <87eem3u4n8.fsf@gnu.org> <875z7f6663.fsf@ambrevar.xyz> <87blh6jl32.fsf@gnu.org> <878scaz0te.fsf@ambrevar.xyz> X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 22 =?utf-8?Q?Vend=C3=A9miaire?= an 229 de la =?utf-8?Q?R=C3=A9volution?= X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-pc-linux-gnu Date: Tue, 13 Oct 2020 23:22:09 +0200 In-Reply-To: <878scaz0te.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Tue, 13 Oct 2020 15:56:45 +0200") Message-ID: <87y2k9g6ta.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guix-devel@gnu.org, Mathieu Othacehe Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Spam-Score: -1.51 X-TUID: UVHk2gOCjCaY Pierre Neidhardt skribis: >> =E2=80=9CSomething=E2=80=9D needs to build the file-to-package database = (which is what >> you=E2=80=99re working on), and then there needs to be a way for users t= o fetch >> that database. This is all orthogonal to substitutes, as I see it, >> which is why I think we need to think about integrating it maybe with >> =E2=80=98guix publish=E2=80=99 on the server side and (guix channels) on= the client >> side. > > If the database is filled on =3Dguix build=3D, then the substitute server > would automatically have a filesearch database. > > Question: How do I hook onto =3Dguix build=3D? You would need a build-completion hook in the daemon, which doesn=E2=80=99t exist (yet!). Note also that at this level we only see derivations, not packages. >> Ah got it; having a database known to correspond to a specific commit is >> even better. >> >> However, note that it could take time for the server to provide the >> complete database for a commit (the time for as many packages as >> possible to be built), so clients may want to refresh it anyway, or even >> perhaps to use an older database. > > Indeed, and that's why I think we need to include a timestamp: if the > client's database timestamp is older than that of the substitute server > database, then we re-fetch it. Yeah, maybe that can work. Thanks, Ludo=E2=80=99.