[asterisk-dev] SIP Stack - Update

[Paul Belanger]

On 12-12-19 05:14 PM, Matthew Jordan wrote:
> On 12/19/2012 03:40 PM, Russell Bryant wrote:
>> On Wed, Dec 19, 2012 at 4:11 PM, Matthew Jordan <mjordan at digium.com
>>> <mailto:mjordan at digium.com>> wrote:
>
>> That common source is EPEL.  I think Paul is suggesting that doing the
>> packaging work there should be the same amount of effort, and likely
>> less in the long run since you would have more help and someone else is
>> managing all of the infrastructure required for building and
>> distributing packages.  Seems like a win win to me ...
>>
>
> Except that we already have infrastructure in place to build packages
> specifically for CentOS. Leveraging that for a new package has a
> quantifiable cost; building out or changing that infrastructure to
> support something else is - at the very minimum - an unknown cost to me
> at this point.
>
> Given that we have a mountain of work for Asterisk 12 to get done, I
> don't see us putting anything else on top of that at this point in time.
> At this point, that includes retooling the packaging infrastructure, or
> supporting EPEL. That picture could certainly change, particularly if a
> lot of people pitch in with the SIP and API projects.
>
> (Note: rough packaging tasks are in Jira and linked off of the SIP
> project page, if anyone is interested :-))
>
Well, at a minimum I believe the packaging repository needs to be public 
and if possible, up on reviewboard.

Right now, submitting patches to existing Digium RPM packages is 
difficult and not properly documented.

-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: 
https://twitter.com/pabelanger