Kudos to whoever pushed the LADSPA SWH plugins to Extras! Thank you!
Now, here's my thoughts: this is a set of LADSPA plugins. It works
strictly in conjunction with the package named "ladspa" - indeed, it is
an extension to it.
Therefore, I believe that the name of the plugins package should include
the string "ladspa" somewhere. Examples:
ladspa-swh-plugins
Or perhaps even more logical:
ladspa-plugins-swh
This name shows clearly the fact that it's actually part of the LADSPA
suite. Moreover, the highest, least specific, denominator (ladspa) comes
first, the second highest (plugins) comes next, while the most specific
denominator (swh) comes last. Kind of like the YYYYMMDD scheme.
My proposal is to settle to a clear rule to name these packages and
apply it consistently to all LADSPA plugins. There are quite a few that
can still go to Extras:
http://ccrma.stanford.edu/planetccrma/software/ladspaworld.html
And this one too:
http://ccrma.stanford.edu/planetccrma/software/soundapps.html#SECTION000625500000000000000
--
Florin Andrei
http://florin.myip.org/
|
