From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel@gnu.org
Subject: Move LV2 plugins to dedicated module?
Date: Mon, 28 Dec 2020 17:09:14 +0100 [thread overview]
Message-ID: <87o8idlxp1.fsf@elephly.net> (raw)
Hi Guix,
we have a whole bunch of LV2 audio plugins. We don’t have a naming
convention for them (there’s no guarantee the name includes “lv2”) and
we seem to be adding these packages to (gnu packages audio) or (gnu
packages music).
What do you think about moving them all to a new module? And what do
you think about finding a naming convention, such as beginning the
package name with “lv2-”?
--
Ricardo
next reply other threads:[~2020-12-28 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 16:09 Ricardo Wurmus [this message]
2020-12-29 11:55 ` Move LV2 plugins to dedicated module? Thorsten Wilms
2020-12-29 12:59 ` Ricardo Wurmus
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=87o8idlxp1.fsf@elephly.net \
--to=rekado@elephly.net \
--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).