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

Prev	Next Index
Date	Thu, 10 Feb 2011 12:02:10 -0800
From	Fernando Lopez-Lezcano <[hidden] at ccrma dot Stanford dot EDU>
To	Paul Davis <[hidden] at linuxaudiosystems dot com>
Cc	Jack-Devel <[hidden] at lists dot jackaudio dot org>

On 02/10/2011 08:18 AM, Paul Davis wrote:
...
> given that packagers feel free to do just about anything to somebody
> else's software, its not really a suprise that ABI breakages can occur
> downstream from our release. it continues to seem like a weak reason
> for justifying the existence of distinctly named libraries called
> "libjack1" and "libjack2".

It is very likely this is done to allow either jack to be installed. For 
that to happen you have to have two packages named differently that 
provide the same "virtual" name so that other packages that depend on it 
can resolve dependencies correctly with either of them.

So you could have, say, "jack1" and "jack2" both providing "jack", 
applications that use jack will require "jack" and then either of the 
servers that is installed would satisfy that. Now, for some reason (a 
Debian policy probably) they split the library from the rest, thus the 
naming.

(I'm not a Debian packager so this may be missing some subtle points)

-- Fernando

Prev	Next Index

1297368362.19528_0.ltw:2,a <4D544442.60705 at localhost>