Over all I do not have anything against, but it might be a more complex process
that some could expect.
A good step was already done with source code restructuring done for v5.0, now
all header files are inside src/ folder, so that can be the base dir when
compiling from sources and can be
Bigger companies have also internal modules, that might be proprietary or too
special to be included in the open source repository. The approach chosen by
sipgate and others to just add this with the Debian patch system works ok, at
least in my experience.
--
You are receiving this because
Well, that is what Sipwise is doing for a long time. You can see their modules
here:
https://github.com/sipwise/kamailio/tree/master/debian/patches/sipwise
Maybe @guillemj or @agranig would like to comment on this request here.
--
You are receiving this because you are subscribed to this
On a different angle - are there modules not in our distribution? Any reason
not to include them in Kamailio? It's not like the asterisk situation where
people may have opinions about Sangoma/Digium licensing schemes and want to
stay outside. We have historically been very open to include
>From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902944
> Hi!
>
> We've got several local kamailio modules, and it would be nice to be
> able to build them separately and not have to hook them into the
> kamailio source and build systems. I suppose others might find this
> useful too.
>
