Hello,
among the topics discussed just before the last major release series (4.0.x) was one about restructuring the source code tree. It started mainly as a proposal to move source code belonging to core in a dedicated folder, but there could be more variants. It's time start discussing if we do it, and if yes, how.
Here is what I could collect so far.
a) no change, keep like it is
b) move source code of core in a dedicated folder named 'core'
c) move all source code in a folder named src, with following sub-structure
src/core - for core src/lib - for internal libraries src/modules - for module
Feel free to propose other variants or express your opinion regarding the proposed options.
Cheers, Daniel
I like option c.
What about stuff under utils that contains code (for example, kamcmd)?
Regards,
Peter
On 07/05/13 14:27, Daniel-Constantin Mierla wrote:
Hello,
among the topics discussed just before the last major release series (4.0.x) was one about restructuring the source code tree. It started mainly as a proposal to move source code belonging to core in a dedicated folder, but there could be more variants. It's time start discussing if we do it, and if yes, how.
Here is what I could collect so far.
a) no change, keep like it is
b) move source code of core in a dedicated folder named 'core'
c) move all source code in a folder named src, with following sub-structure
src/core - for core src/lib - for internal libraries src/modules - for module
Feel free to propose other variants or express your opinion regarding the proposed options.
Cheers, Daniel
2013/5/7 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
among the topics discussed just before the last major release series (4.0.x) was one about restructuring the source code tree. It started mainly as a proposal to move source code belonging to core in a dedicated folder, but there could be more variants. It's time start discussing if we do it, and if yes, how.
Here is what I could collect so far.
a) no change, keep like it is
b) move source code of core in a dedicated folder named 'core'
c) move all source code in a folder named src, with following sub-structure
+1 for c.
-- With best regards, Peter Lemenkov.
Is there any discussion to be had about things that are currently compile-time options that should be runtime or modules?
It's been discussed before (and I don't know if there is an easy way to do it), but it'd be nice to have SCTP as a module.
I am sure some people out there must have some favourite compile-time options that'd be nice to have as runtime (in kamailio.cfg) options too.
Regards,
Peter
On 07/05/13 14:27, Daniel-Constantin Mierla wrote:
Hello,
among the topics discussed just before the last major release series (4.0.x) was one about restructuring the source code tree. It started mainly as a proposal to move source code belonging to core in a dedicated folder, but there could be more variants. It's time start discussing if we do it, and if yes, how.
Here is what I could collect so far.
a) no change, keep like it is
b) move source code of core in a dedicated folder named 'core'
c) move all source code in a folder named src, with following sub-structure
src/core - for core src/lib - for internal libraries src/modules - for module
Feel free to propose other variants or express your opinion regarding the proposed options.
Cheers, Daniel
On 5/7/13 3:40 PM, Peter Dunkley wrote:
Is there any discussion to be had about things that are currently compile-time options that should be runtime or modules?
It's been discussed before (and I don't know if there is an easy way to do it), but it'd be nice to have SCTP as a module.
I am sure some people out there must have some favourite compile-time options that'd be nice to have as runtime (in kamailio.cfg) options too.
It's on my plan to create a sctp module to collect the code depending on the external libs. Still a bunch of code related to sctp will be in core, but no longer a compile time option.
Anyhow, this topic can be approached during next irc meeting as well to see if something else can be moved as a module to avoid re-compilation.
Cheers, Daniel
Regards,
Peter
On 07/05/13 14:27, Daniel-Constantin Mierla wrote:
Hello,
among the topics discussed just before the last major release series (4.0.x) was one about restructuring the source code tree. It started mainly as a proposal to move source code belonging to core in a dedicated folder, but there could be more variants. It's time start discussing if we do it, and if yes, how.
Here is what I could collect so far.
a) no change, keep like it is
b) move source code of core in a dedicated folder named 'core'
c) move all source code in a folder named src, with following sub-structure
src/core - for core src/lib - for internal libraries src/modules - for module
Feel free to propose other variants or express your opinion regarding the proposed options.
Cheers, Daniel
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
-
Daniel-Constantin Mierla -
Peter Dunkley -
Peter Lemenkov