unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Re-approaching package tagging
Date: Tue, 18 Dec 2018 12:29:46 +0100	[thread overview]
Message-ID: <87imzrgjit.fsf@gnu.org> (raw)
In-Reply-To: <875zvsq8ov.fsf@dustycloud.org> (Christopher Lemmer Webber's message of "Mon, 17 Dec 2018 14:01:20 -0500")

Hello,

Christopher Lemmer Webber <cwebber@dustycloud.org> skribis:

> In the past when we've discussed package tagging, I think Ludo' has been
> against it, primarily because it's a giant source of bikeshedding.  I
> agree that it's a huge space for bikeshedding... no space provides more
> bikeshedding than naming things, and tagging things is a many to many
> naming system.

The reason I’m unconvinced about tags is that I used to be a big fan of
them, back when debtags was introduced (long ago!), but then I had to
face reality: people (me included) would just do plain text searches,
not sophisticated tag queries.

> However, I will say that finding packages based on topical interest is
> pretty hard right now.  If I want to find all the available roguelikes:
>
> cwebber@jasmine:~$ guix package -A rogue
> hyperrogue	10.5	out	gnu/packages/games.scm:3652:2
> roguebox-adventures	2.2.1	out	gnu/packages/games.scm:1047:2

I’m surprised you don’t mention --search, which is more appropriate than
-A (‘-A’ is here only to search among package names):

--8<---------------cut here---------------start------------->8---
$ guix package -s roguelike | recsel -p name,relevance
name: roguebox-adventures
relevance: 7

name: tome4
relevance: 5

name: crawl
relevance: 5

name: crawl-tiles
relevance: 5

name: cataclysm-dda
relevance: 5

name: angband
relevance: 5
--8<---------------cut here---------------end--------------->8---

I’m very much in favor of improving ‘--search’ until we’re happy with
the results it gives.

WDYT?

Ludo’.

  parent reply	other threads:[~2018-12-18 11:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 19:01 Re-approaching package tagging Christopher Lemmer Webber
2018-12-17 20:57 ` swedebugia
2018-12-17 23:08   ` zimoun
2018-12-18  7:48   ` Catonano
2018-12-18 11:34     ` Catonano
2018-12-19  6:51     ` swedebugia
2018-12-19  7:42       ` swedebugia
2018-12-18 11:29 ` Ludovic Courtès [this message]
2018-12-18 14:54   ` Christopher Lemmer Webber
2018-12-18 10:36     ` zimoun
2018-12-19 15:04       ` Ludovic Courtès
2018-12-18 20:46         ` zimoun
2018-12-19 23:12           ` zimoun
2018-12-20  7:53             ` Ludovic Courtès
2018-12-20  9:44               ` Chris Marusich
2018-12-21 21:00                 ` Ludovic Courtès
2018-12-20 10:57               ` Christopher Lemmer Webber
2018-12-20 11:55                 ` swedebugia
2018-12-21 21:06                 ` Ludovic Courtès
2018-12-19 15:05     ` Ludovic Courtès
2018-12-18 20:48       ` zimoun
2018-12-20  7:55         ` Ludovic Courtès
2018-12-20 14:42           ` zimoun

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=87imzrgjit.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=cwebber@dustycloud.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).