From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#35551: guix search Date: Sat, 11 May 2019 14:18:27 -0400 Message-ID: <874l6026sx.fsf@netris.org> References: <1666426.mZ6LCf6Yd0@omega> <8736lmypsm.fsf@gnu.org> <87sgtm0xuw.fsf@netris.org> <1724203.DhVHnQV9by@omega> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:41499) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPWcJ-0001DF-H4 for bug-guix@gnu.org; Sat, 11 May 2019 14:21:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hPWcI-0007p1-MP for bug-guix@gnu.org; Sat, 11 May 2019 14:21:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:55717) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hPWcI-0007op-JB for bug-guix@gnu.org; Sat, 11 May 2019 14:21:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hPWcI-0001Um-CZ for bug-guix@gnu.org; Sat, 11 May 2019 14:21:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <1724203.DhVHnQV9by@omega> (Bruno Haible's message of "Sat, 11 May 2019 00:38:41 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Bruno Haible Cc: 35551-done@debbugs.gnu.org Hi Bruno, Bruno Haible writes: > Mark H Weaver wrote: >> If we add functionality that calls out to the network in response to a >> package search, e.g. to query popularity ratings or package file >> listings, we should make sure the user knows it's happening, and provide >> a way to disable it. Some users may not want information about their >> package searches to be leaked to the outside world. > > Good point. > > Would it be more acceptable, upon 'guix search', to download an incremental > update of a package popularity database, and do the search locally? This > way, only the fact that the user has been doing a 'guix search' would be > leaked to the outside world, not the search term. Yes, that would address my concerns, although popularity ratings might be compact enough and change slowly enough that it might be sufficient to simply have them embedded in the Guix source code and manually updated periodically. Popularity ratings would also be useful to set build priorities on our build farms. The package file listings, on the other hand, are likely to be so large that it's not practical to download an incremental update of all of them. Thanks, Mark