1 Jul
2009
1 Jul
'09
9:13 p.m.
On 07/01/2009 07:50 PM, Juha Heinanen wrote:
--
Daniel-Constantin Mierla
http://www.asipto.com/
Daniel-Constantin Mierla writes:
btw, I forgot to mention, if by asking a possibility to configure the
name for binary, tools, etc. you mean that you will implement and submit
a patch when it is the case, that is very fine, improvements are welcome
always.
What I wanted to say is that I do not want replacing defaults with other
static names now. And I won't put efforts in such things before we get
to testing phase for new relase.
Daniel
I do not think every utility has to be renamed.
Anyhow there are kamctl
and serctl that do different things and they have to be kept.
i'm not asking renaming of all utilities. in fact, i'm not asking to
rename any, but a POSSIBILITY to configure the name of serctl that deals
with core and should thus be independent from ser or kamailio.
Also
rtpproxy was in the cvs repository as a related project, so keeping this
kind of related tools with different names should be fine. Related are
also serweb, sems, etc ... sticking to current name is better imo.
all those you list are not mandatory for managing of the core like
serctl is and i don't care how they are named. if you want to stick to
ser ralated name of serctl, then do so, but don't force everyone else
to do the same.
-- juha