On Wed, 2009-10-07 at 14:28 -0400, Dale Worley wrote: > OK, now a third opinion: sipx-config does two very distinct things: > "sipx-config --java", which tells about the platform's Java > configuration, and "sipx-config --version", which gives the versions of > all the sipXecs components. The first is a tool used by many > components, the second is a tool that describes all the components. > Perhaps the two functions should be separated? > > > From a user perspective, I'd rather see this list be available as an > > output of the existing sipx-config script (sipx-config --components).
Revising my proposal: Right now, sipx-config does two very different things, which should be part of two different components: sipx-config --java This is configuration information about the underlying platform, and is needed as input by various sipXecs components (at run time, not build time). As such, it is reasonable that sipx-config is part of sipXportLib, which is where it is now. sipx-config --version and the proposed sipx-config --components These are configuration information about sipXecs, and as such, should be part of the sipXecs component. Within this context, I think that sipx-config needs to be split. Since people use "sipx-config --version" directly, I propose to rename the --java function to "sipx-config-java" or maybe something more neutral like "sipx-config-platform". The script "sipx-config" will be moved to the sipXecs component, and will get the --components functionality added. Dale _______________________________________________ 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/
