Re: Update: Scheduling another freeze of Jack-related packages
Colin Watson <cjwatson@debian.org> writes:
> Can I suggest that, in the future, it would be a good idea to rename the
> jack-audio-connection-kit source package each time a new soname appears?
> That way, the old and new versions could coexist in testing and you
> wouldn't have this transition pain every time. You'd have to make
> another upload of the old source package to stop it building jackd, but
> that shouldn't be a significant problem compared to the current bad
> situation.
If I understand correctly what you are proposing, it may not always
work correctly.
Since JACK is a "Connection Kit", all its clients must connect to the
same jackd process. Sometimes the protocol or some shared memory
structures change between JACK releases. When this happens, the
JACK_PROTOCOL_VERSION is incremented, causing jackd to refuse
connections from down-level libraries.
There have generally been fewer incompatibilities introduced in the
application <-> libjack interface than in the libjack <-> jackd
interface.
--
joq
Reply to: