2014-01-27 Alessio Treglia <[email protected]> > Hi all, > > On Sun, Jan 26, 2014 at 8:55 PM, Jaromír Mikeš <[email protected]> > wrote: > > Alessio, Adrian can you comment pls? > > I never managed to solve it once and for all mostly because it seems > upstream is not taking it as an important issue. > The thing is: we can do it but I'm not sure most client applications > are ready to deal with it properly though. > IMHO we'd better file a bug upstream to ask for a clear standard > policy for both clients and plugins first. >
We really should clarify this. I encounter few issues already: 1) When updating synthv1 samplv1 drumkv1 LV2 plugins I realize that upstream using paths like this: /usr/lib/lv2/synthv1.lv2/synthv1.so /usr/lib64/lv2/synthv1.lv2/synthv1_ui.so /usr/lib64 shouldn't be used on debian ... After some discussion with him he send me a patch ... Now all *.so files are installed this way: /usr/lib/x86_64-linux-gnu/lv2/synthv1.lv2/synthv1.so /usr/lib/x86_64-linux-gnu/lv2/synthv1.lv2/synthv1_ui.so This is perfect by debian policy by I am afraid about compatibility with other DAW and plugins hosts. At least Rui as upstream of Qtractor collaborate. 2) Here is already one issue with Qtractor http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734937 3) We have also opened bug against Caps plugins which are LADSPA http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690115 Just the request to make them multi-arch Should we consider this? best regards mira
_______________________________________________ pkg-multimedia-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
