On 2023-10-29 17:45:56 +0100, Sebastian Ramacher wrote: > On 2023-10-29 07:01:07 -0700, Erich Eickmeyer wrote: > > Sebastian, > > > > I'm fairly certian Robin Gareus made it quite clear what Jeremy was saying > > in his reply: > > > > >The LV2 FHS that Jeremy mention can be found at > > >https://lv2plug.in/pages/filesystem-hierarchy-standard.html > > > > > >Now you may not like, or disagree with the official standard, but breaking > > it is not acceptable. This affects various >3rd party software, notably > > Reaper, Harrison Mixbus, Ardour and other non-free DAWs that expect LV2 > > plugins in >/usr/lib/lv2/ > > > > > > > > >LV2s are to be installed $PREFIX/lib/lv2 (unrelated to $LIBDIR). > > >Most LV2 plugin build systems use LV2DIR = $PREFIX/lib/lv2 for this. > > > > This does divert from the standard location in which shared libraries are > > expected to be located, but LV2 plugins, as you are aware, are not normal > > shared libraries. If they cannot be found in /usr/lib/lv2, then it literally > > breaks the functionality of several DAWs out there, including Ardour (which > > we ship). Sure, users can always manually add the search path of > > /usr/lib/$(DEB_HOST_MULTIARCH)/lv2 to the software, but that's an > > unnecessary inconvenience. > > lilv does not install LV2 plugins. If other packages abuse lilv's libdir > as base to determine LV2DIR, those packages are buggy. As you explain > above, it's not $libdir/lv2 but $prefix/lib/lv2 that's to be used.
FWIW, the only packages in Debian installing LV2 plugins in multi-arch locations are mda-lv2 and naspro-bridges. Fixes for both have been uploaded to unstable. Cheers -- Sebastian Ramacher
