On Wed, 2006-12-20 at 21:11 -0500, Paul Davis wrote:
the "standard" specifies that LADSPA_PATH be
used if set. thus, distros
that package LADSPA should set LADPSA_PATH in /etc/profile and its
various equivalents.
Ok, then maybe a good solution for now is to have our ladspa package
generate an /etc/profile.d/ladspa.sh file at install-time that exports a
system-dependent LADSPA_PATH, like
export
LADSPA_PATH=$HOME/.ladspa/sse2:$HOME/.ladspa:/usr/local/lib/ladspa/sse2:/usr/local/lib/ladspa:/usr/lib/ladspa/sse2:/usr/lib/ladspa
...for sse2-enabled platforms (for instance).
Then plugin packagers can build and install any number of different
plugin builds as long as they land in directories known by the ladspa
package installer.
Same goes for DSSI_PATH.
AG