Re: Re: lv2fil

[Jaromír Mikeš]

> Od: Free Ekanayaka <free at 64studio.com>

JM> Actually there should be probably one executable file ..."ui"

FE> Right, but if I got it correctly, that's a python script, not a binary
FE> executable. In theory it should got to /usr/share. However if we
FE> decide that LV2 plugins should be an exception to the rule, because of
FE> the LV2 architecture recommendation, then it's fine to have lintian
FE> override of that warning.
 
JM> By default this plugin installation ask for LV2_PATH environment variable
JM> and wants install there.
JM> I am building package in pbuilder there is not LV2_PATH set , so I set
JM> installation dir to /usr/lib/lv2 in debian/rules.
 
FE> Okay.
 
JM> BTW: How will be LV2_PATH set on system? Manually? By installation
JM> of some package? lv2core, slv2?
 
FE> IMO, we shouldn't rely on an environment variable at all. The programs
FE> we include in our packages should just do the right thing without
FE> setting any variable. Ideally the programs should automatically search
FE> for plugins in /usr/lib/lv2 (while still giving priority to LV2_PATH,
FE> which can be set explicitly by the user if he/she wants), if this is
FE> not the case for some program the relevant package should patch it and
FE> possibly push the patch upstream.

This make things clear ... thanks

mira