From: Bruno Haible <bruno@clisp.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 35551-done@debbugs.gnu.org
Subject: bug#35551: guix search
Date: Sat, 11 May 2019 00:38:41 +0200 [thread overview]
Message-ID: <1724203.DhVHnQV9by@omega> (raw)
In-Reply-To: <87sgtm0xuw.fsf@netris.org>
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.
Bruno
next prev parent reply other threads:[~2019-05-10 22:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 22:57 bug#35551: package gcc does not depend on binutils and glibc Bruno Haible
2019-05-03 23:27 ` Nicolas Goaziou
2019-05-04 0:20 ` Tobias Geerinckx-Rice
2019-05-04 1:34 ` Bruno Haible
2019-05-07 16:23 ` Tobias Geerinckx-Rice
2019-05-07 17:26 ` Bruno Haible
2019-05-07 16:04 ` Ludovic Courtès
2019-05-09 21:21 ` Ricardo Wurmus
2019-05-09 21:57 ` Bruno Haible
2019-05-10 6:18 ` Ricardo Wurmus
2019-05-10 8:07 ` Ludovic Courtès
2019-05-10 9:38 ` bug#35551: guix search Bruno Haible
2019-05-10 10:17 ` Ludovic Courtès
2019-05-10 10:22 ` Bruno Haible
2019-05-10 15:17 ` Ludovic Courtès
2019-05-10 14:21 ` Bruno Haible
2019-05-10 21:15 ` Ludovic Courtès
2019-05-10 22:04 ` Mark H Weaver
2019-05-10 22:38 ` Bruno Haible [this message]
2019-05-10 23:41 ` Tobias Geerinckx-Rice
2019-05-11 18:38 ` Mark H Weaver
2019-05-11 18:18 ` Mark H Weaver
2019-05-13 7:57 ` Ludovic Courtès
2019-05-13 15:39 ` znavko
2019-05-10 15:43 ` znavko
2019-05-10 21:22 ` Bruno Haible
2019-05-10 10:18 ` Bruno Haible
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1724203.DhVHnQV9by@omega \
--to=bruno@clisp.org \
--cc=35551-done@debbugs.gnu.org \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).