* Move LV2 plugins to dedicated module?
@ 2020-12-28 16:09 Ricardo Wurmus
2020-12-29 11:55 ` Thorsten Wilms
0 siblings, 1 reply; 3+ messages in thread
From: Ricardo Wurmus @ 2020-12-28 16:09 UTC (permalink / raw)
To: guix-devel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Move LV2 plugins to dedicated module?
2020-12-28 16:09 Move LV2 plugins to dedicated module? Ricardo Wurmus
@ 2020-12-29 11:55 ` Thorsten Wilms
2020-12-29 12:59 ` Ricardo Wurmus
0 siblings, 1 reply; 3+ messages in thread
From: Thorsten Wilms @ 2020-12-29 11:55 UTC (permalink / raw)
To: Ricardo Wurmus; +Cc: guix-devel
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>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Move LV2 plugins to dedicated module?
2020-12-29 11:55 ` Thorsten Wilms
@ 2020-12-29 12:59 ` Ricardo Wurmus
0 siblings, 0 replies; 3+ messages in thread
From: Ricardo Wurmus @ 2020-12-29 12:59 UTC (permalink / raw)
To: Thorsten Wilms; +Cc: guix-devel
Hi Thorsten,
> How about one module for both LV2 and LADSPA plugins, though?
Sounds good. “audio-plugins.scm”?
> A naming convention like lv2- would be most welcome.
OK!
> Moving definitions from one module to another won’t affect any
> installation, right?
That’s right, no impact.
> But I take it name changes break at least the
> upgrade chain, so users should be made aware of that.
This is no problem if we define deprecations. When users run “guix upgrade”
they will automatically get the packages with the new names.
--
Ricardo
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-12-29 13:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-28 16:09 Move LV2 plugins to dedicated module? Ricardo Wurmus
2020-12-29 11:55 ` Thorsten Wilms
2020-12-29 12:59 ` Ricardo Wurmus
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).