[asterisk-dev] Asterisk now available with bundled pjproject!

[George Joseph]

On Wed, Mar 23, 2016 at 12:21 AM, Luar Roji <cyberplant at gmail.com> wrote:

> Tested here:
> https://hub.docker.com/r/luar/asterisk/builds/buddnqfztv8zsf8zsgtxjj8/
>
> And seems to be working fine, nice!
>

​Great!  Thanks for the feedback.​




>
> On Mon, Mar 7, 2016 at 4:28 PM, George Joseph <george.joseph at fairview5.com
> > wrote:
>
>> The current Asterisk 13 and master git branches have a new feature that
>> will be included in 13.8.0:  The ability to compile and run Asterisk with a
>> bundled version of pjproject.
>> ​​
>>
>> Why would you want to do this?  Several reasons:
>>
>>    - Predictability:  When built with the
>>    ​bundled
>>     pjproject, you're always certain of the version you're running
>>    against, no matter where it's installed.
>>    - Scalability:  The default pjproject configuration is optimized for
>>    client applications. The bundled version's configuration is optimized for
>>    server use.
>>    - Usability:  Several feature patches, which have been submitted
>>    upstream to pjproject but not yet released, have been included in the
>>    bundled version.
>>    - Safety:  If a security or critical issue is identified in
>>    pjproject, it can be patched and made available with a new release of
>>    Asterisk instead of
>>    ​having to ​
>>    waiting for a new release of pjproject
>>    ​​
>>    .
>>    - Maintainability:  You don't need to build and install separate
>>    packages.
>>    - Supportability:  When asking others for help, there's no question
>>    about which version of pjproject you're using and what options it was
>>    compiled with.
>>    - Compatibility:  This is especially important from a development
>>    perspective because it means we can be sure that new pjproject APIs that
>>    have been introduced
>>    ​,​
>>    or old ones that have been deprecated
>>    ​,​
>>    are handled and tested appropriately in Asterisk.
>>    - Reliability:  You can be sure that Asterisk was tested against the
>>    bundled version.
>>
>>
>> So now that you're sold, here's how you use it:
>>
>> All you have to do is add the "--with-pjproject-bundled" option to your
>> ./configure command line and remove any other "--with-pjproject" option you
>> may have specified.  The configure and make processes will download the
>> correct version of pjproject, patch it, configure it, build it and finally
>> link Asterisk to it statically.  No changes in runtime configuration are
>> required.
>>
>> Still not sold?  The default behavior hasn't changed so as long as you
>> haven't specified "--with-pjproject-bundled", your build and deploy process
>> remains as is.
>>
>> PLEASE TRY THIS!!  I'd love some feedback BEFORE 13.8.0 is released.
>>
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>>
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20160323/a53fc0d3/attachment-0001.html>