Packaging ardour 4.0

[Jaromír Mikeš]

2015-04-20 15:49 GMT+02:00 Adrian Knoth <adi at drcomp.erfurt.thur.de>:

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.



I am using get-orig-source in rules file
Recently I've used repacking from git in ntk package ... you can have a
look for inspiration.


>
>  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.
>

I updated a bit copyright file ... mostly just dropped files which has been
dropped upstream too.
So there will be second run to add file which has been added  upstream ;)

At least lintian yield less wild output now.

regards

mira
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20150421/30ecc3d7/attachment.html>