[asterisk-dev] conflicting timer modules

[Philipp Kempgen]

Tzafrir Cohen schrieb:
> On Sun, Feb 15, 2009 at 01:06:04PM +0100, Johansson Olle E wrote:

>> > On Sun, Feb 15, 2009 at 3:48 PM, Tzafrir Cohen <tzafrir.cohen at xorcom.com 
>> > > wrote:

>> >> 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.

Yup. I learned it's a good idea to keep asking yourself "How would
I package this" while writing software.


    Philipp Kempgen
-- 
AMOOCON 2009, May 4-5, Rostock / Germany   ->  http://www.amoocon.de
Asterisk: http://the-asterisk-book.com - http://das-asterisk-buch.de
AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied  ->  http://www.amooma.de
Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998
--