unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Fabio Pesari <fabiop@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Adding tags to packages
Date: Sun, 03 Jan 2016 15:33:22 +0100	[thread overview]
Message-ID: <877fjqu40d.fsf@gnu.org> (raw)
In-Reply-To: <568828EF.7050406@gnu.org> (Fabio Pesari's message of "Sat, 2 Jan 2016 20:45:51 +0100")

Fabio Pesari <fabiop@gnu.org> skribis:

> In short, I think tags are a simple solution to a problem that's been
> around for many years, and the fact that it wasn't done properly in the
> past is purely anecdotal and doesn't mean it can't be done properly now.

As discussed before¹, even though I’m sympathetic to the approach, I
believe experience suggests that tags are not a success.

The main reason is probably that it provides a UI that’s more “complex”
than plain-text/regexp search, and that plain-text search works “well
enough” most of the time.

As Alex writes, one can always choose not to use tags; this would be an
argument for implementing them.  However, it seems to me that the cost
of implementing and maintaining them would be high enough (the
implementation itself may not be that trivial if we want a query
language, i18n, RDF(?), and whatnot.)

What about exploring ways to improve --search?

I can think of a very simple improvement to make: make it so that

  guix package -s '\<board\>' -s game

returns packages that match *both* regexps instead of one or the other
as is currently the case?  We could make a similar change in guix.el.

A second idea would be to rank search matches based on the number of
occurrences of the regexps and their location (package name
vs. description.)

Thoughts?

Thanks,
Ludo’.

¹ https://lists.gnu.org/archive/html/guix-devel/2015-07/msg00198.html

  parent reply	other threads:[~2016-01-03 14:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-02 19:45 Adding tags to packages Fabio Pesari
2016-01-03  9:02 ` Alex Kost
2016-01-03 14:20   ` Ludovic Courtès
2016-01-03 14:34     ` Fabio Pesari
2016-01-03 15:04       ` Ludovic Courtès
2016-01-03 15:31         ` Fabio Pesari
2016-01-03 22:37           ` Ludovic Courtès
2016-01-03 14:33 ` Ludovic Courtès [this message]
2016-01-03 16:22   ` Ricardo Wurmus
2016-01-03 17:15     ` Ludovic Courtès
2016-01-04  9:19       ` Pjotr Prins
2016-01-04 23:30   ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2015-07-08  7:41 Pjotr Prins
2015-07-08  9:24 ` John Darrington
2015-07-08 12:55   ` Ludovic Courtès
2015-07-08 13:55   ` Pjotr Prins

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=877fjqu40d.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=fabiop@gnu.org \
    --cc=guix-devel@gnu.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).