Branching Asterisk for EPEL

Jeffrey Ollie jeff at
Fri Dec 21 15:12:28 UTC 2007

On 12/21/07, Thorsten Leemhuis <fedora at> wrote:
> k; the biggest problem with this scheme is: what if other packages want
> to use a similar tricks when they need a new gtk, qt, <insert other
> libs>. That could soon become a maintenance pita and a kind of second
> library layer ontop of (or in parallel) the libs from RHEL, which afaics
> nobody wants. Thus we might need to limit this and put some hurdles in
> the way; something like "such packages must be approved by the EPEL SIG
> in a meeting" or something like that.

Yeah, I don't really want to get into maintaining a copy of speex - I
think that I'll poke the RHEL speex maintainer and see if we can't
work something out.  If that doesn't work we'll have to wait for RHEL6
to branch Asterisk.


More information about the epel-devel-list mailing list