jack2 packaging

[Robin Gareus]

On 06/14/2013 03:47 PM, Adrian Knoth wrote:
> 
> Frankly, I don't like your idea of splitting the package and defining a
> conflict between them. There has to be a better solution which allows
> for co-installation.
> 
> One could further split the jackd2 package into something like
> 
>    - jackd2-backends (all the .so files)
>    - jackd2-jackd (depends on jackd2-backends)
>    - jackd2-jackdbus (depends on jackd2-backends)
> 
> 
> and allow both jackd2-jackd{,dbus} packages to be co-installable.

+1

I suggested the same solution to Kaj in some inadvertently off-list
email exchange.

A short except from that email:

In short the motivation for that is:

 * jackdbus is single instance (per session), but dynamic settings
 * jackd2 has fixed settings but allows multiple instances.

Jackdmp from upstream allows to have both around, the current debian
package allows that too.

Please improve the packaging, package-naming and break jackd/bus out
into separate packages,... but don't make them conflict. That would be a
regression.

Cheers!
robin