Packaging ardour 4.0

[Adrian Knoth]

On 04/20/15 15:09, Jaromír Mikeš wrote:

> Great!
>
> How do you do repacking? Manually?

Sort of. I track upstream git and then drop the waf binary. I wish the
filter statement in gbp.conf would work, but for some reason it doesn't.

> P: ardour3 source: source-contains-autogenerated-visual-c++-file
> MSVCvst_scan/vst_scan.rc.in <http://vst_scan.rc.in>
> P: ardour3 source: source-contains-autogenerated-visual-c++-file
> MSVCvst_scan/resource
> P: ardour3 source: source-contains-autogenerated-visual-c++-file
> MSVCardour3/resource
> P: ardour3 source: source-contains-autogenerated-visual-c++-file
> icons/win32/resource
> P: ardour3 source: source-contains-autogenerated-visual-c++-file
> icons/win32/msvc_resources.rc.in <http://msvc_resources.rc.in>

These should indeed be dropped. If you can figure out some magic to do
this automatically, that would be great. There's automatic
git-upstream-repackaging in CDBS, I've used it for jackd2, so taking a
look at jackd2's debian/rules should get you started.

> E: ardour3: menu-icon-too-big usr/share/pixmaps/ardour4.xpm: 48x48 > 32x32
> Should we ship smaller icon?

No, I think lintian is wrong here. I have a HiDPI display (2560x1600 on
13" screen), and small icons are a pain. OSX (the only OS that has
properly working HiDPI out of the box) ships icons up to 1024x1024, so
lintian's 32x32 restriction is a total joke.


Is it already possible to have SVG logos?

> I will have a look on copyright file later ... now busy

Thanks, that's clearly an area I don't like to bother with at all, but I
understand its importance.



Cheers