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

Le Thu, 10 Feb 2011 13:32:25 -0500,
Paul Davis <[hidden]> a écrit :

> On Thu, Feb 10, 2011 at 1:16 PM, Dominique Michel
> <[hidden]> wrote:
> 
> > With gentoo, the dependences are not pre-compiled on a distant
> > server but what have been compiled and installed into the machine
> > by portage. You can change the dependences (as example, an extreme
> > case, move from jack1 to jack2), a single command "revdep-rebuild"
> > will recompile the programs against the new dependencies and fix
> > the whole system,
> 
> this is itself a small problem when applied to JACK.
> 
> the whole point of API *and* ABI compatibility is that no such
> recompile is actually necessary. a system that rebuilds all JACK
> clients when the version of JACK changes *regardless of the nature of
> that change* is a system that is doing the wrong thing.
> 
> so although there are some distinct differences between the way gentoo
> does things and the way debian and its cousins do things, gentoo
> doesn't or shouldn't do anything any different when the installed
> version of JACK is changed, for the most part.

You are right, it was just a (bad) example. I never tried it with
jack. Also, when it is an API change in some lib, 2 versions can
generally coexist by using slots (as example different versions of
python and the associated programs). And this is not the case with jack
because of its API and ABI compatibility.

-- 
"We have the heroes we deserve."

1297364292.11637_0.ltw:2,a <20110210195444.7d65cd49 at tuxstudio dot homenetwork>