From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: Re: Re-approaching package tagging
Date: Tue, 18 Dec 2018 00:08:18 +0100 [thread overview]
Message-ID: <CAJ3okZ0x5gW6oNiqaBgDQfzGumP22gPDHR9TyWjSHoh7uwHQLA@mail.gmail.com> (raw)
In-Reply-To: <aa2467cc-bed7-68e8-ffe2-7e3ba9cac541@riseup.net>
Dear,
Does the command `guix package -s rogue` fit your needs ?
Because `--search` search in synopsis and description.
Then `ruby-multi-test` is false-positive, I guess.
And `nethack` does not show up. Maybe because the description and/or
synopsis is not verbose enough.
If `guix package -s rogue -s dungeon | recsel -C -p name` then more
package are found. Do they correspond? e.g., powwow?
What is the feedback about the Debian tagging system debtags?
I mean that I am an happy user of Debian and I do not use so much
debtags. Because I do not often explore packages and so I find the
`aptitude search` regexp then grep easier to remember.
Well, other said, from my point of view, a tag system does not solve
the issue here and it adds layer (bikeshedding?).
The easiest fix seems to improve the descriptions field. IMHO.
Or to add features to --search and regexp.
In complement to the more elegant solution proposed by swedebugia.
What do you think?
All the best,
simon
next prev parent reply other threads:[~2018-12-17 23:08 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 [this message]
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
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=CAJ3okZ0x5gW6oNiqaBgDQfzGumP22gPDHR9TyWjSHoh7uwHQLA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--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).