Re: [Jack-Devel] lib{j, tsch}ack{, 1, 2} [Was: Jack "capsule/container" implementation?]

PrevNext  Index
DateThu, 10 Feb 2011 11:13:08 -0600
From Jack O'Quin <[hidden] at gmail dot com>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
CcJack-Devel <[hidden] at lists dot jackaudio dot org>
In-Reply-ToPaul Davis Re: [Jack-Devel] lib{j, tsch}ack{, 1, 2} [Was: Jack "capsule/container" implementation?]
On Thu, Feb 10, 2011 at 11:01 AM, Paul Davis <[hidden]> wrote:
> On Thu, Feb 10, 2011 at 11:22 AM, Gabriel M. Beddingfield
> <[hidden]> wrote:
>
>> And that's more or less what they did.
>>
>> Debian has libjack0 (Jack1) and libjack-jackd2-0.  They both "provide"
>> libjack0.
>
> given that the server and the client library need to be synced at all
> times, i am confused why anyone would ever provide a "libjack"
> package. the package, surely, is "jack" or "jack1" or "jack2", not
> "libjack-anything" (given "jack"'s availability, hence
> "jack-audio-connection-kit")

I remember them explaining it years ago, before jack2.

There are quite a few packages that link to libjack and conditionally
use JACK (if it is running), but use some other interface if it is
not. Their packages must depend on libjack to make that test.

Some users objected, however, to installing a "daemon" without their
knowledge and explicit permission. These were mostly people who do not
use JACK at all. Since jackd looks like a "daemon" from their
perspective, the packagers decided on a separate server package
(mainly to shut them up, I suspect).
-- 
 joq
PrevNext  Index

1297359346.916_0.ltw:2,a <AANLkTi=MJg_+6KqiSQO5hFzv4XF3QVaodCYo=ibBSTV4 at mail dot gmail dot com>