From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Taylan Kammer <taylan.kammer@gmail.com>
Cc: Raghav Gururajan <rg@raghavgururajan.name>,
jgart <jgart@dismail.de>, Mark H Weaver <mhw@netris.org>,
LibreMiami <packaging-guix@libremiami.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>,
guix-devel@gnu.org
Subject: Re: Search improvements (Was: Opposition to new single-letter package name "t")
Date: Tue, 09 Mar 2021 17:18:38 +0100 [thread overview]
Message-ID: <87h7lkmhb5.fsf@nckx> (raw)
In-Reply-To: <446cc95b-9068-e07d-80ee-fbcc887c2c65@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
Taylan,
Taylan Kammer 写道:
> This discussion made me realize that "guix search" might benefit
> from
> the following improvement though: I think the relevance score
> for a
> search result should be increased significantly if the searched
> word is
> a standalone (not substring) part of a package's name when the
> name is
> split into dash-separated words.
Thanks for remembering ‘guix search’! It didn't occur to me at
all.
For most upstreams whether or not dashes were in vogue[0] when
they named their project is literally arbitrary. We'd penalise
many other packages like texlive-todonotes, open{ssh,vpn,*},
ktexteditor, r-performanceanalytics, qutebrowser, ... It's not a
net win.
If I might pet my own peeve, I think clever heuristics appear
necessary in part because %package-metrics grossly overscores
package names. Rank them *below* synopsis & description--which
will contain the name anyway--with a metric of 1, maybe 2. Enough
to keep the relevant stuff above the irrelevant stuff (python- >
ruby-, etc.) without distorting things as they do now.
Kind regards,
T G-R
[0]: Not a joke.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-03-09 17:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 5:27 Opposition to new single-letter package name "t" Mark H Weaver
2021-03-09 5:39 ` Raghav Gururajan
2021-03-09 5:47 ` jgart
2021-03-09 6:08 ` Raghav Gururajan
2021-03-09 9:35 ` Leo Prikler
2021-03-09 11:38 ` Tobias Geerinckx-Rice
2021-03-09 11:40 ` Julien Lepiller
2021-03-09 13:09 ` Ricardo Wurmus
2021-03-09 12:40 ` Raghav Gururajan
2021-03-09 18:12 ` Nicolas Goaziou
2021-03-10 0:16 ` Mark H Weaver
2021-03-09 13:32 ` Search improvements (Was: Opposition to new single-letter package name "t") Taylan Kammer
2021-03-09 15:12 ` zimoun
2021-03-09 16:18 ` Tobias Geerinckx-Rice [this message]
2021-03-09 18:37 ` zimoun
2021-03-09 21:39 ` bug#47028: Discourage single-character package names Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-09 21:41 ` bug#47028: [PATCH 1/2] doc: Discourage ambiguous " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-09 21:41 ` bug#47028: [PATCH 2/2] lint: Warn about single-character " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-26 8:26 ` zimoun
2021-04-01 8:51 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-04-01 20:41 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-09 21:51 ` bug#47028: [PATCH 1/2] doc: Discourage ambiguous " Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-03-10 0:44 ` bug#47028: Discourage single-character " Mark H Weaver
2021-03-10 11:28 ` Ludovic Courtès
2021-03-10 13:04 ` zimoun
2021-04-01 8:57 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=87h7lkmhb5.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
--cc=mail@nicolasgoaziou.fr \
--cc=mhw@netris.org \
--cc=packaging-guix@libremiami.org \
--cc=rg@raghavgururajan.name \
--cc=taylan.kammer@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.