On 07/01/2009 08:15 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
there is a problem now because of different database schemas. if you use kamailio modules, then you have to stick to kamctl and not use serctl.
i'm not using kamctl to manage database tables. serctl with mi extension is all i need and it seems to work fine for the modules that i use.
sometimes this is the easy way for many - not using, not care - but leaves the project in an incoherent state, which I prefer to avoid as much as possible.
Probably was a bit of rush from me this time, trying not to get other renamings in very short time and then fix backwards.
From what you say, adding a way to change easily names, is just fine for me.
Thanks, Daniel
All these renaming done right now will create confusion as many things get broken while testing and most of documentation is not updated.
how many times i need to say that i'm not asking to rename anything.
It is very easy to do a search/replace in code, but what about all references in web documentation?
currently man pages refer to sip-router web site. if you want them to refer to kamailio web site instead, then we need to make another copies of them.
I fail to see the reason for all this mess right now, when we haven't finished with code integration. For those writing docs to help testers is hard to manage all those. I wrote wiki tutorials that shows how to get default config file running with sip router core. Just have in mind that ad-hoc renaming breaks many things.
you don't seem to be reading what i write. i'm not proposing to rename anything.
-- juha