From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#35551: guix search Date: Fri, 10 May 2019 18:04:44 -0400 Message-ID: <87sgtm0xuw.fsf@netris.org> References: <1666426.mZ6LCf6Yd0@omega> <3642152.sbCaK8LMaK@omega> <87sgtm1umd.fsf@gnu.org> <6987474.668M4leDEz@omega> <8736lmypsm.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:54315) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPDfT-0007Vh-Oi for bug-guix@gnu.org; Fri, 10 May 2019 18:07:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hPDfS-0001UG-Tv for bug-guix@gnu.org; Fri, 10 May 2019 18:07:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:54036) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hPDfS-0001U0-Gy for bug-guix@gnu.org; Fri, 10 May 2019 18:07:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hPDfS-0006Ba-AK for bug-guix@gnu.org; Fri, 10 May 2019 18:07:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <8736lmypsm.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 10 May 2019 23:15:21 +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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: Bruno Haible , 35551-done@debbugs.gnu.org Hi, Ludovic Court=C3=A8s writes: > Bruno Haible skribis: > >>> For that we=E2=80=99d need to resort to an external service providing t= his info. >> >> Why would it need to be an external service? Can't you incorporate >> this information in a data file that you ship as part of the >> distribution? > > Such a file would quickly become stale, it=E2=80=99d have to be updated f= rom an > external service anyway. 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. Thanks, Mark