Bug#758888: lmms: Provide links to LADSPA plugins in /usr/lib/ladspa

[Tobias Doerffel]

Hi,

as one of the former main developers of LMMS I'd like to write a few
words about LMMS and LADSPA. LMMS ships a bundle of LADSPA plugins in
order to provide a standardized set of sound effects. Standardized
means, the set is the same on every platform and distribution. When
users create projects with LMMS and use our bundled plugins, it's
guaranteed that the project will work and sound the same everywhere.
If you decide to drop our plugins and depend on a package which
formally provides the same file it can still happen that things are
different and do not work as expected due to version differences.

Best example: CAPS LADSPA plugins. We have been shipping CAPS 0.4.x
for years now and the available plugins and their behaviour remained
stable for the users all the time. If you would depend on
https://packages.debian.org/jessie/caps instead, lots of effects would
be missing when loading a project as the available plugins inside CAPS
have changed significantly between 0.4.x and 0.9.x. If you'd simply
rename caps.so to caps-lmms.so no plugins would be loaded at all as
the library base name (caps) is saved in the project file (internally
we load caps.so, caps.dll or caps.dylib depending on the platform). If
we (LMMS developers) decide to switch to 0.9.x we will implement an
according upgrade mechanism internally (and probably even still
provide CAPS 0.4.x in a separate library) so things don't break for
the user.

So please help us to provide an optimal user experience for LMMS users
on Debian. Don't break LMMS by removing files from an LMMS
installation even though I understand that redundancy is bad. If you
have questions, feel free to ask.

Best regards

Toby