On 03/10/2009 03:59 PM, Ovidiu Sas wrote:
I started a new section on the wiki to keep track of what needs to be done for modules that are not compiling: http://sip-router.org/wiki/devel/kamailio-integration#module_integration_sta...
Let me know if you think that this will help and what kind of improvements are required.
it is very good. I added extra columns to underline the dependency part and description of that, plus status where to map: done, discarded, etc...
Cheers, Daniel
Regards, Ovidiu Sas
On Tue, Mar 10, 2009 at 9:40 AM, Jan Janak jan@iptel.org wrote:
On 10-03 09:32, Ovidiu Sas wrote:
Having the OPENSER_OID defined inside the snmstats module should work.
OK.
I think that all k module (except tm) should be part of a single branch. Like this, one fix in a module can be visible for other modules that relay on it. It will make compile fixes to be solved faster.
Eventually yes, I'll see if I can setup another branch which will have all module specific branches merged.
The reason why I setup the repository this way, having one branch per module, is that I wanted to have module changes separated. This way I can always do/undo changes to a particular module and still keep others unaffected.
The primary purpose of the kamailio-3.0 repository is to generate patches, when we eventually get to the state where all modules compile, work, and people are happy with the changes, we will generate a set of patches and apply it to the svn repository when/if the code in the svn repository switches to the sip-router core.
After that the kamailio-3.0 repository can be decomissioned because it will no longer be necessary.
Jan.
Kamailio (OpenSER) - Devel mailing list Devel@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel http://lists.openser-project.org/cgi-bin/mailman/listinfo/devel