1 Jul
2009
1 Jul
'09
1:15 p.m.
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. 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.
BTW gen_ha1 is something very simple to do from command line:
echo -n "user:domain:password" | md5sum | $AWK '{ print $1 }'
Daniel
On 07/01/2009 05:54 PM, Juha Heinanen wrote:
Andrei Pelinescu-Onciul writes:
that is what you get when/if the plan is to have build several products
with different names from the same sources. a common name sip-router
would have been fine with me, but not with some other people. vote on
this is still to be done, however.
-- juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla
http://www.asipto.com/
How about only installing using a different name?
Let it compile to
sercmd, but make install would install it under UT_NAME (one could
do a sed -e 's/^ser/$(UT_NAME)' in install-utils:).
since utils/sercmd/Makefile has
NAME=sercmd
it would be cleaner to add to Makefile.defs
SERCMD_NAME=sercmd and then in utils/sercmd/Makefile replace the above
with
NAME=$(SERCMD_NAME)
and then in main Makefile
utils_bin_install= utils/gen_ha1/gen_ha1 utils/sercmd/$(SERCMD_NAME)
on the other hand, why can't installation be done in
utils/sercmd/Makefile under name NAME?
and also
in modules_s/ctl/ctl_defaults.h instead of ser:
#define DEFAULT_CTL_SOCKET "unixs:/tmp/ser_ctl"
That would be even more tricky. You would have to fix possible mentions
in the docs and even then differently named sercmds will use
different default
sockets => lost of "support" problems.