asterisk into unstable

[Tzafrir Cohen]

So how do we move forward with getting Asterisk into Unstable?

The newer libpri and the DAHDI packages are prerequirements.

As it has to spend time in the new queue anyway, I wonder if it won't be
best to go for Asterisk 1.6.1 and experiment with the alternative timing
sources. I guess that even if they don't really work well on 1.6.1, they
will work well by the time 1.6.2 is released, and hence it may be useful
to add the following two subpackages:

  asterisk-dahdi:
    chan_dahdi.so
    res_timing_dahdi.so
    codec_dahdi.so
    app_dahdibarge.so
    app_dahdiras.so
    app_dahdiscan.so

  asterisk-timing-pthread:
    res_timing_pthread.so

Both packages will provide "asterisk-timing" and the main asterisk
package will depend on:

  asterisk-dahdi | asterisk-timing

As for the moment we'll still default to the DAHDI timing source, until
a new one proves useful.

The over-engeneering here is because 1.6.2 has a third timing source:
res_timing_timerfd .

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