On Fri, 2009-10-09 at 12:31 -0400, Dale Worley wrote: > On Fri, 2009-10-09 at 12:20 -0400, Scott Lawrence wrote: > > It might be easier to leave the existing sipx-config --java alone, and > > instead enhance the (also existing) sipxecs-config to add the > > --components argument. > > The problems with that are: (1) sipxecs-config doesn't exist (*), and > (2) it doesn't split the sipx-config --java function (which really ought > to be in sipXportLib) and the sipx-config --version function (which > really ought to be in sipXecs). (Although I suppose that "sipx-config > --version" could be grandfathered to invoke "sipxecs-config --version".)
sorry ... I was thinking that the --version should also be moved into sipxecs-config. This would mean that that 'top level' script would not be generated from the common template that generates the others. > (*) The next chapter of this discussion regards components that do not > have a sip*-config script to print their configured version. grumble.... yes, well, fixing that is pretty trivial _______________________________________________ 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/
