Hi
On Thu, Apr 01, 2010 at 10:25:18PM -0500, Tim Nelson wrote:
> Hello all- **
>
> A few weeks ago (maybe more) another user posted an inquiry about the
> status of Callweaver development and the project as a whole.
> Unfortunately, I don't believe there were any replies of substance to
> the question. So, I'd like to pose the same inquiry...
>
> What is the status of Callweaver? I see there has been progressive
> development, or at least recent 'changesets' [1] to the codebase(stopped
> Feb 14th, Valentines day related? :-) ), but a release has not been made
> since nearly a year ago. Checking the milestones [2], the project seems
> to be severely behind 'schedule'. While not a problem in and of itself,
> it would be nice to know what the roadblocks are to the project's
> development. Is it manpower, funding, equipment, etc?
Frankly I'm not even sure what is the current main developement branch.
Trunk seems to require an extra library that I have to build myself. Is
there any interest in it?
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.
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?
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 .
--
Tzafrir Cohen
icq#16849755 jabber:[email protected]
+972-50-7952406 mailto:[email protected]
http://www.xorcom.com iax:[email protected]/tzafrir
_______________________________________________
Callweaver-dev mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-dev
