Re: lv2fil

[Jaromír Mikeš]

> Od:  <adi at drcomp.erfurt.thur.de>

JM> > W: lv2fil source: dh-make-template-in-source debian/manpage.1.ex
JM> > Should I write man pages even there is no binary and it is not library?

AK> Not sure. If this would be BSD, there would be a manpage for it. ;)

AK> I suggest to use a very generic one, like: "This is a filter, it has
AK> four bands, and upstream url is..."


JM> > W: lv2fil: image-file-in-usr-lib usr/lib/lv2/filter.lv2/lv2logo.png
JM> > http://lintian.debian.org/tags/image-file-in-usr-lib.html

AK> Not sure about this one. Is there something like --share-dir? As far as
AK> I know LV2 (and that's close to nothing), the idea is to have all the
AK> files in one directory.

JM> > W: lv2fil: script-not-executable ./usr/lib/lv2/filter.lv2/ui
JM> > http://lintian.debian.org/tags/script-not-executable.html

JM> > These issues happened also if I've installed manually from source.
JM> > Should I try to solve them in packaging process or should I ask upstream? 

AK> The logo issue could be discussed with upstream. Since ui is a python
AK> script, it would be possible to dynamically change the location upon
AK> invocation or write it at compile time.
 
AK> On the other hand, this might ruin the whole LV2 idea. From lv2plug.in:

AK> --- cut ---   
AK> Bundles
 
AK> Everything a LV2 plugin needs is bundled inside a directory, which can
AK> easily be handled as a whole while still allowing direct access to the
AK> parts.
 
AK> --- cut ---

AK> This would mean "lintian override". (probably for both warnings) ;)

Hi Adrian,

thanks for feedback and testing.
There is probably needed a discussion, there will be hopefully some other lv2 packages soon.
We should know how to deal with these issues.

Free? Reinhard? others?
thanks for comments

mira