[asterisk-dev] Module Deprecation, Default Not Building, and Removal

Joshua C. Colp jcolp at sangoma.com
Tue Oct 6 13:22:18 CDT 2020

On Fri, Oct 2, 2020 at 4:18 PM Jared Smith <jaredsmith at jaredsmith.net>

> On Fri, Oct 2, 2020 at 11:50 AM Dan Jenkins <dan at nimblea.pe> wrote:
>> sorry, I thought I was agreeing with you :) we need to engage package
>> maintainers to potentially help ease the shift - if packages are a
>> thing.... but as far as I'm concerned most package managers have out of
>> date versions of Asterisk, or don't have things you want so you end up
>> building from source anyway
> I actively package Asterisk for Fedora and EPEL (CentOS/RHEL), and I work
> hard to package the latest versions as they are released.  I'm always open
> to additional input on how to make my packages more relevant for consumers
> -- either by packaging additional modules, or by having better
> sub-packages.  For example, my packages already have chan_sip and pjsip
> split off as separate subpackages.

As a packager and someone who has been in the community and user world,
what's your opinion and thoughts on the 2 year strategy?

Joshua C. Colp
Asterisk Technical Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20201006/1304a9fe/attachment.html>

More information about the asterisk-dev mailing list