packaging jack...

[Gabriel M. Beddingfield]

On Sat, 17 Apr 2010, Jonas Smedegaard wrote:

>> stop right here.
>> the library and the daemon are tied together.
>> the protocol between jackd and libjack is NOT fixed.
>> 
>> (basically i consider it a mistake to even have libjack and jackd in
>> different packages) but it might make sense to have that.
>
> The separation of library and daemon is so that an application can link 
> against the library without forcing the daemon to be installed: the JACK 
> support might be optional for that application (without it being a plugin 
> that can be packaged separately from the main application.

When you register with libjack, it will start the daemon if 
it is not already running.  So, you can't have the library 
without the daemon.[*]

-gabriel

[*] There is a trivial case where an application is
     using libjack only for the ringbuffer implementation.
     This wouldn't require the daemon, and I doubt that
     any applications are /only/ using this part.