Re: JACK 0.91.1-1
On Tue, 13 Jan 2004, Robert Jordens wrote:
> We had a request from Junichi for a "mini-freeze" around JACK in
> November. I don't know if that really is still valid because the goal of
> that freeze is reached and the timetable for the release changed a lot.
> I think we can do it and push another recompile.
>
> Meanwhile JACK 0.94.0 is in the wild. API impact is non-existant but it
> fixes important aspects of the command-line-parsing. My upload will be
> based on that.
Yes, great :)
But ....
Its good news that the API didn't change between 0.80.0 and 0.94.0,
unfortunately we have 0.75.0 in testing, which is not compatible.
This means that if we update jack and related packages now, we will
have the same problem that we had with 0.75.0, that is it takes
about half a year to get them into testing.
If we do not upload a new jack, it is a lot easier to update the
applications and get them into testing directly.
Hmm,...
The solution would be to somehow automatically recompile everything
against jack. This is theoretically easy and would most likely be
successful.
In practice I don't know, ...
Maybe we have to establish a "jack mini NMU policy", which means
that those packages that are not updated and compiled against the
new jack within say 10 days are NMU'd.
Guenter
Reply to: