From: znavko@disroot.org
To: "Ludovic Courtès" <ludo@gnu.org>, "Mark H Weaver" <mhw@netris.org>
Cc: Bruno Haible <bruno@clisp.org>, 35551-done@debbugs.gnu.org
Subject: bug#35551: guix search
Date: Mon, 13 May 2019 15:39:29 +0000 [thread overview]
Message-ID: <cb73ed41279956561da0afb1375b5b54@disroot.org> (raw)
In-Reply-To: <877eauvla9.fsf@gnu.org>
Thank you, Ludovic. It will be nice to have some additional fields computed with Internet databases like:
Tag->name
Tag->Relevance
Purpose: editor, viewer, library, development tool
Interface: gui app, console-only, console and gui, system calls
For every tag needs to determine relevance.
For example, package VLC:
Tag->name: video
Tag->relevance: 100
Tag->name: view
Tag->relevance: 90
and other tags
Purpose: viewer
Interface: gui app
This can give additional options for search or just improve sorting when user type f.e. ' guix search video viewer'
May 13, 2019 7:58 AM, "Ludovic Courtès" <ludo@gnu.org> wrote:
> Hi Mark,
>
> Mark H Weaver <mhw@netris.org> skribis:
>
>> Bruno Haible <bruno@clisp.org> 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.
>
> FWIW, I like that there’s a purely off-line mode for ‘guix search’, as
> is currently the case (after all, none of Guix relies on any single
> service so far, and I think that’s a nice property.)
>
> However, I think it’d be nice to have the option to enhance search
> results by resorting to external services—just like using a substitute
> service “enhances” the user experience.
>
> I agree that the approach should rather be to download a complete
> database and operate locally on it, rather than give the exact query to
> the server.
>
> Thanks,
> Ludo’.
next prev parent reply other threads:[~2019-05-13 15:40 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cb73ed41279956561da0afb1375b5b54@disroot.org \
--to=znavko@disroot.org \
--cc=35551-done@debbugs.gnu.org \
--cc=bruno@clisp.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.