From: Thorsten Wilms <t_w_@freenet.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Move LV2 plugins to dedicated module?
Date: Tue, 29 Dec 2020 12:55:57 +0100 [thread overview]
Message-ID: <20201229125557.d1741d0f44d1483f5c29c13d@freenet.de> (raw)
In-Reply-To: <87o8idlxp1.fsf@elephly.net>
On Mon, 28 Dec 2020 17:09:14 +0100
Ricardo Wurmus <rekado@elephly.net> wrote:
> 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-”?
Hi! Since noone else more involved chimed in so far:
I didn’t even notice that some plugins are in packages/music. I think
at at minimum, all audio plugins should be in the same module. Rather
audio than music, I’d say.
How about one module for both LV2 and LADSPA plugins, though?
A naming convention like lv2- would be most welcome.
Moving definitions from one module to another won’t affect any
installation, right? But I take it name changes break at least the
upgrade chain, so users should be made aware of that.
--
Thorsten Wilms <t_w_@freenet.de>
next prev parent reply other threads:[~2020-12-29 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 16:09 Move LV2 plugins to dedicated module? Ricardo Wurmus
2020-12-29 11:55 ` Thorsten Wilms [this message]
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=20201229125557.d1741d0f44d1483f5c29c13d@freenet.de \
--to=t_w_@freenet.de \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).