jack2 packaging

Adrian Knoth adi at drcomp.erfurt.thur.de
Fri Jun 14 13:47:35 UTC 2013


On 06/05/2013 07:18 AM, Kaj Ailomaa wrote:

>>>> I'd like to go ahead and change this in packaging, making jackdbus
>>>> and jackd separate for jack2. Also, make jackdbus conflict with
>>>> jackd. But, that is only if there are no bad implications from
>>>> doing this, and I currently know of none.
>>> I really like having both around. If possible, please do not make
>>> them conflict.

>>> I use jackdbus as main jackd (runs most of the time and automatically
>>> switches backends depending on connected interfaces). I also regularly
>>> use jackd for a 2nd or 3rd instance -- most of the time for debug
>>> purposes e.g. running ardour in valgrind without interfering with the
>>> main jackdbus, but also for multiple indep jack sessions on the same
>>> machine w/ different audio-interfaces.

>> I can see the point in being able to run multiple instances of jack,
>> which is quite possible with jackd. But, why - from a user point of
>> view - would you ever want to run both jackd and jackdbus at the same
>> time?

He wants jackdbus for all the fancy stuff and jackd for tasks usually
required by developers.

Since Robin has contributed substantially to Ardour (the recent timecode
changes, the video timeline, MIDI plugin functionality and so on and so
forth), I'd say it's safe to assume he knows what he is talking about.
;)

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. Of
course, people can still mess it up, but at least there's a clear
separation for those who want "easy" and "I can have both" for those who
need it.


And while we're at it, let's move the manpages and the debconf files to
jackd-defaults to avoid code duplication between jackd1 and jackd2.




Cheers



More information about the pkg-multimedia-maintainers mailing list