On Tue, Apr 06, 2010 at 09:29:35PM +0300, Tzafrir Cohen wrote: > Frankly I'm not even sure what is the current main developement branch.
Trunk > Trunk seems to require an extra library that I have to build myself. Is > there any interest in it? Absolutely. What is the library? Is there a ticket open? > Is there any interest in providing packages of the whole Unicall stack? > I can easily provide it, but so far I had no real reason to upload them > to e.g. Debian (apart from SpanDSP). This complex stack (some 3 or 4 > layers of dependencies) makes life interesting for anybody who want to > build CallWeaver. Dunno. I don't use Debian and at this stage I'm not packaging anything for anyone although others might. > Another issue is: has anybody looked into the security advisories by > Asterisk to see which of them applies to CallWeaver? Have the relevant > fixes been applied? I keep an eye on them. I don't fix everything though (for instance I just don't care about chan_iax). > When I wanted to package CallWeaver (1.2.1 (?)) for Debian I encountered > some issues with automake. Specifically, modules would get rebild on > 'make install DESTDIR=$(CURDIR)/debian/tmp . That's because 1.2 always builds the core as a library so when libtool installs it it has to relink every module. Trunk (aka dev aka pre-2.0) doesn't unless the local DSO support is incapable of exporting symbols from the main binary (and frankly that build type for those systems is untested in recent memory) so it doesn't have to relink. Mike -- Mike Jagdis Web: http://www.eris-associates.co.uk Eris Associates Limited Tel: +44 7780 608 368 Reading, England Fax: +44 118 926 6974 _______________________________________________ Callweaver-dev mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-dev
