On Mon, 2010-03-15 at 15:54 -0400, JOLY, ROBERT (ROBERT) wrote: > I got it but on the other hand, I do not have the skills to do such a > change quickly with a high level of confidence that RPMs, upgrades and > ISO build won't be broken and I cannot afford the time to learn my way > through this at the moment. I understand your argument about the > blob-effect but I do not think that two additional lines are going to > break that 850-line-camel's back. If that is okay with you, I'll > quickly edit the sipxecs start-up script to get this blocking 4.1.7 > issue off by back and open a tracker to do the clean-up. That > clean-up activity will eventually get scheduled and assigned when time > and resources allow for it. Is that acceptable to you?
Sure - send me the issue # and I'll pick it up. > Our startup scripts are already taken care of but I have not touched > the openfire startup script and do not intend on changing it because > of licensing issues. Once they do deliver the Apache 2.0-license > version of Openfire, we can revisit this. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
