> libspeex has split out some functions which have been under active > development still into a separate library libspeexdsp. > Applications which used these symbols will need to be fixed to > link with it and rebuilt from source. Opal is one of those apparently.
> libspeex will conflict with the current version of it in its next > upload, and I've cloned this report to opal for action with it. Ron, If the API has changed then the soname should also change as well, just conflicting with the previous version is not sufficient and doesn't make for a smooth library transition. Given the wide spread deployment of speex we need to tread softly, which was why we had left the beta versions in experimental, to try and identify these issues and ensure a smooth transition. I know upstream speex say the beta is stable, but if it is so stable, then why don't they release 1.3 final?? Mark
signature.asc
Description: This is a digitally signed message part.
