Re: Bug#205552: jack-audio-connection-kit: new upstream release available
Robert Jordens <robertjo@phys.ethz.ch> writes:
> We didn't have so many releases of JACK. You can follow its history
> under (you can even subscribe to its development news and bugreports,
> hint, hint ;-):
I did subscribe, thanks.
> http://packages.qa.debian.org/j/jack-audio-connection-kit.html
A very informative page. I had not seen it.
> > The new transport features and the amd64 sized int work we are doing
> > *are* binary compatible with previous releases to a very high degree.
>
> Does "high degree" mean "everywhere except the old transport functions
> failing and JACK breaking compatibility on AMD64"? I guess that sounds
> very reasonable.
Yes.
The old transport functions still mostly work. The client side is
fully supported. I could not get the old transport master interface
working correctly with the new features, so I stubbed it out. In the
few existing transport master applications (mainly ardour 0.9beta),
the application will run, but its transport commands are ignored by
other applications. Not a disaster. From an end-user perspective
this is better than declaring it incompatible, so it doesn't run at
all.
> He is doing it all by himself. He can recompile his stuff whenever he
> wants to and everyone will install his newly compiled applications
> because they all use his repository.
Nando's "distribution" is quite different from Debian. I mention it
as evidence that JACK compatibility *has* been tested and *does* work.
This was in no way intended as a negative comparison with Debian
policy decisions. I respect Debian's committment to quality and
stability. That's why I use it. :-)
Regards,
--
Jack O'Quin
Austin, Texas, USA
Reply to: