From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 58136@debbugs.gnu.org, Lars-Dominik Braun <lars@6xq.net>
Subject: [bug#58136] [PATCH] ui: Improve sort order when searching package names.
Date: Sat, 01 Oct 2022 23:42:54 +0200 [thread overview]
Message-ID: <87v8p3b4pt.fsf@gnu.org> (raw)
In-Reply-To: <86wn9na82p.fsf@gmail.com> (zimoun's message of "Wed, 28 Sep 2022 16:26:38 +0200")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> Well, I propose something like see below (based on your patch):
>
> 1. keep the weight as 4
> 2. set the “namespace” weight to 1 (or 2 if you prefer)
>
> Otherwise, for example, generic name as CSV could artificially bump
> the relevance and hide relevant packages. For instance, compare
>
> guix search csv
>
> 3. use upstream-name if provided
Maybe something like:
(define %package-metrics
`((,package-name . 4)
(,package-upstream-name* . 4) ;or a lower weight, dunno
…))
where:
(define (package-upstream-name* package)
(or (assoc-ref (package-properties package) 'upstream-name)
(package-name-sans-namespace package))) ;strip "r-", "emacs-", etc.
WDYT?
(Perhaps ‘package-upstream-name’ could be taught about these implicit
name conversions done for R, Python, Emacs, etc.?)
Ludo’.
next prev parent reply other threads:[~2022-10-01 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 9:27 [bug#58136] [PATCH] ui: Improve sort order when searching package names Lars-Dominik Braun
2022-09-28 14:26 ` zimoun
2022-09-28 20:23 ` Maxime Devos
2022-09-28 20:45 ` Maxime Devos
2022-09-28 21:40 ` zimoun
2022-09-28 21:43 ` Maxime Devos
2022-10-01 21:42 ` Ludovic Courtès [this message]
2022-10-02 8:26 ` zimoun
2022-10-12 11:24 ` Lars-Dominik Braun
2022-10-17 7:46 ` Ludovic Courtès
2022-10-17 8:19 ` zimoun
2022-12-09 11:49 ` Lars-Dominik Braun
2022-12-13 13:28 ` bug#58136: " Ludovic Courtès
2022-12-13 14:53 ` [bug#58136] " Lars-Dominik Braun
2022-12-13 16:40 ` Ludovic Courtès
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=87v8p3b4pt.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=58136@debbugs.gnu.org \
--cc=lars@6xq.net \
--cc=zimon.toutoune@gmail.com \
/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.