[asterisk-dev] conflicting timer modules

[Tzafrir Cohen]

On Sun, Feb 15, 2009 at 01:06:04PM +0100, Johansson Olle E wrote:
> 
> 15 feb 2009 kl. 12.29 skrev Jim Boykin:
> 
> > keep either posix or dahdi time, res_timer_*
> >
> > On Sun, Feb 15, 2009 at 3:48 PM, Tzafrir Cohen <tzafrir.cohen at xorcom.com 
> > > wrote:
> >> Hi
> >>
> >> In trunk (1.6.2) I see that the separate res_timing_* module conflict
> >> with each other. In 1.6.1 I don't see it.
> >>
> >> Why is this conflict? Is it merely a run-time issue or also a build- 
> >> time
> >> issue? Is it enforced on build-time or on run-time?
> >>
> Shouldn't menuselect take care of at least trying to avoid these kind
> of conflicts?

I build a package that should support both types of timing. I will
probably put res_timing_dahdi in a separate package (asterisk-dahdi .
Along with chan_dahdi, a number of dahdi-related apps and probably also
app_meetme).

I prefer not to have to patch Asterisk to do this.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir