From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Tagging packages
Date: Wed, 23 Feb 2022 23:25:04 +0100 [thread overview]
Message-ID: <20220223222504.Bg2xirOuI6E_heqrlcPZUJoblYOBks_zTCcU5JaIS2c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22191@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
New comment by tibequadorian on void-packages repository
https://github.com/void-linux/void-packages/issues/22191#issuecomment-1049272789
Comment:
I think tags like biology, astronomy are not that important. (Not because I don't see these fields as important but because I don't think there's so much software related to this in the repos?)
Tags could also be useful for things like audio plugins where there are LV2, LADSPA, DSSI, VST... plugins which could be tagged as such.
next prev parent reply other threads:[~2022-02-23 22:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 5:05 [ISSUE] " anjandev
2020-05-22 5:14 ` xmksv
2020-05-23 4:52 ` GithubPrankster
2020-05-24 2:09 ` ericonr
2020-05-24 2:20 ` ericonr
2020-05-24 2:53 ` anjandev
2020-05-24 3:14 ` ericonr
2020-05-26 6:15 ` Anachron
2020-05-26 8:02 ` travankor
2020-05-26 8:41 ` flexibeast
2020-05-26 14:16 ` Vaelatern
2020-05-26 16:28 ` ericonr
2020-05-26 16:29 ` ericonr
2020-05-26 16:29 ` ericonr
2020-05-26 16:39 ` Vaelatern
2020-05-26 17:56 ` Duncaen
2020-05-27 5:15 ` Vaelatern
2020-05-27 19:12 ` pullmoll
2020-05-30 17:53 ` leahneukirchen
2022-02-23 21:45 ` motorto
2022-02-23 21:46 ` motorto
2022-02-23 22:23 ` tibequadorian
2022-02-23 22:24 ` tibequadorian
2022-02-23 22:24 ` tibequadorian
2022-02-23 22:25 ` tibequadorian [this message]
2022-02-24 18:17 ` motorto
2022-02-24 23:14 ` Anachron
2022-05-26 2:13 ` github-actions
2022-06-10 2:13 ` [ISSUE] [CLOSED] " github-actions
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=20220223222504.Bg2xirOuI6E_heqrlcPZUJoblYOBks_zTCcU5JaIS2c@z \
--to=tibequadorian@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).