binary compatibility [was: Re: [asterisk-dev] Corydon76 Issue Deleted: 0006925, 04-28-06 17:49 Corydon76 Issue Deleted: 0006920]

[Tzafrir Cohen]

On Mon, May 01, 2006 at 07:52:23AM -0500, Kevin P. Fleming wrote:
> Anton wrote:
> 
> > There is a number of modules in fact, which are exist in the 
> > binary form, and quite complicated to get them rebuilt or 
> > updated to a new version, so if there is a way to keep 
> > binary compatibility it should be kept.
> 
> I'm not aware of any other open source projects that attempt to preserve
> binary compatibility across major release versions. Certainly it is not
> the norm, and is an undue burden on the developers of the open source
> project to have to maintain compatibility for non-open-source modules.

Debian has a number of asterisk-related modules that are not part of the
main asterisk package. The most notable examples are asterisk-app-fax
and packages built from asterisk-addons.

For that reason I have asked you in this mailing list a while ago if the
binary interface to modules is expected to remain stable along the 1.2
series. You have answered that it is. Later on it was broken in 1.2.5 
(for a good cause, IIRC).

-- 
Tzafrir Cohen      sip:tzafrir at local.xorcom.com
icq#16849755       iax:tzafrir at local.xorcom.com
+972-50-7952406           
tzafrir.cohen at xorcom.com  http://www.xorcom.com