[asterisk-users] Mixing commercial/SVN Asterisk

[Danny Nicholas]

"Shouldn't" is a better word.  Some will work, others won't.  Buyer beware.

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Richard Kenner
Sent: Wednesday, December 16, 2009 3:10 PM
To: asterisk-users at lists.digium.com
Subject: Re: [asterisk-users] Mixing commercial/SVN Asterisk

> You should not try to mix modules for different major versions of
> Asterisk. 1.6.0.x modules should only be used with 1.6.0.x, etc.
> 
> While John's previous comments were not incorrect, it is unfortunately
> quite common that there are API/ABI changes between major releases that
> necessitate different versions of Digium's binary modules to be built.
> We don't normally build them in advance of a major release (since the
> APIs may not be stable), but once they reach the 'release candidate'
> state we start building them and testing them internally. They are then
> released in parallel with the actual Asterisk release, so the 1.6.2.x
> compatible modules will be released with Asterisk 1.6.2.0.

So in other words, my original statement was correct: if I'm running
a release candidate or from the SVN, I can't use thse components.
Right?

_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users