[SCM] jackd2 packaging branch, master, updated. debian/1.9.5.dfsg-13-18-g7c7e31a

[Reinhard Tartler]

On Tue, Jun 15, 2010 at 15:55:02 (CEST), Adrian Knoth wrote:

> On Tue, Jun 15, 2010 at 01:35:54PM +0000, adiknoth-guest at users.alioth.debian.org wrote:
>
>> The following commit has been merged in the master branch:
>> commit 0732d192e10a578b76d9075cdf0136445cae6304
>> Author: Adrian Knoth <adi at drcomp.erfurt.thur.de>
>> Date:   Tue Jun 15 14:38:26 2010 +0200
>> 
>>     Drop libjack-dev from jackd2.
>>     
>>     Only jackd1 provides the dev package.
>
> Huu, this will result in a major usability issue. While it's fine for
> the buildds to always use jackd1, it's inconvenient for users who want
> to run jackd2 AND compile some jack apps on their own.
>
> It's a rather common use case, and given that jackd2 will be the default
> in squeeze, we need to address this issue.
>
>
> Is there a well-known approach? If not, here are the facts:
>
>   * libjack-dev header files are fine also for jackd2 users
>
>   * /usr/lib/pkgconfig/jack.pc: Dunno. Probably ok.
>
>   * /usr/lib/libjack(server).a: Does anybody care?
>
>   * /usr/lib/libjack(server).so are two symlinks to the full (package
>     specific) version number, e.g., libjack.so.0.0.28.
>
>     As long as jackd1 and jackd2 don't differ in the SOVERSION, we could
>     manually symlink libjack.so->libjack.so.0 instead.
>
>
> I guess libjack-dev then needs to depend on libjack0 | libjack-0.116, so
> it can be installed with both jackd versions but still fetches libjack0
> on buildds.
>
> If there are better approaches, please let me know.

How about making jackd2 provide a binary package 'libjack-jackd2-dev'
that conflicts with libjack-dev?

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4