On 03/27/2009 01:08 PM, Andrei Pelinescu-Onciul wrote:
On Mar 27, 2009 at 11:00, Daniel-Constantin Mierla <[email protected]> wrote:
Hello,
I was thinking to a new idea of repository structure.
The core and libraries do not overlap, so no conflict here. For modules
have three directories:
- modules - store common integrated modules now (tm, db drivers) and
modules that exist only in one project
- modules-k - K modules that overlap in name with S modules or other
particular K modules not moved to "modules" directory
- modules-s - S modules that overlap in name with K modules or other
particular S modules not moved to "modules" directory
As soon a new integration is done for overlappin modules, it will be
moved to modules and removed for modules-k/modules-s
The advantage I see is only one repository. The disavantage is updating
the makefile to work with three module directories for a period of time.
Opinions?
What should: make all and make install do? (which set of modules)
all modules
How would the installed version look like? (all module in the same dir?)
different dirs:
/usr/local/lib/sip-router/modules
/usr/local/lib/sip-router/modules-k
/usr/local/lib/sip-router/modules-s
If you run make all and then start ./sr with loadmodule "textops" in
sr.cfg, which textops version will be used, the on from k or from s?
there could be full path or mpath for each:
mpath="/usr/local/lib/sip-router/modules"
loadmodule "tm.so"
mpath="/usr/local/lib/sip-router/modules-k"
loadmodule "textops.so"
mpath="/usr/local/lib/sip-router/modules-s"
loadmodule "auth.so"
Cheers,
Daniel
If we manage to find some good answers to the above questions, then we
could go for it.
BTW: we don't even need same repos, if we have separate dirs, we could
experiment with git submodules (which basically tell that a subdir
content should be fetched from another repo).
Andrei
On 02/26/2009 09:53 PM, Juha Heinanen wrote:
Andrei Pelinescu-Onciul writes:
if i make a commit on a k module, i just call the script again and
get a
new version of k compiled.
Yes, that would work (manually copying), but I find that more difficult
than it should be (everybody will have to use some script and have at
least 2 local repos, one for sip-router and one for the modules).
i don't see having two repos on the local disk as a problem. before
copying, the script updates both automatically to latest level. i can
write the script and post it on the list once the repos are in place.
i see it a much bigger problem if the same thing (sip-router) source is
in two different places.
-- juha
_______________________________________________
sr-dev mailing list
[email protected]
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla
SIP Router Masterclass - Kamailio (OpenSER) Training
http://www.asipto.com/index.php/sip-router-masterclass/
_______________________________________________
Kamailio (OpenSER) - Devel mailing list
[email protected]
http://lists.kamailio.org/cgi-bin/mailman/listinfo/devel
http://lists.openser-project.org/cgi-bin/mailman/listinfo/devel
--
Daniel-Constantin Mierla
SIP Router Masterclass - Kamailio (OpenSER) Training
http://www.asipto.com/index.php/sip-router-masterclass/
_______________________________________________
Serdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/serdev
