On Dec 9, 2009, at 2:29 PM, Dale Worley wrote: > > On Fri, 2009-12-04 at 18:20 -0500, Scott Lawrence wrote: >> On Fri, 2009-12-04 at 17:31 -0500, Dale Worley wrote: >>> Following up on Thursday's scrum: The current builds contain the >>> following RPM names (with some of the trailing version identifiers >>> removed): >>> >>> sipxfreeswitch-4.1.0 >>> >>> sipx-freeswitch-1.0.4 >>> sipx-freeswitch-codec-passthru-amr-1.0.4 >>> sipx-freeswitch-codec-passthru-g723_1-1.0.4 >>> sipx-freeswitch-codec-passthru-g729-1.0.4 >>> sipx-freeswitch-devel-1.0.4 >>> sipx-freeswitch-lang-en-1.0.4 >>> sipx-freeswitch-lua-1.0.4 >>> sipx-freeswitch-perl-1.0.4 >>> sipx-freeswitch-spidermonkey-1.0.4 >>> >>> sipxopenfire-4.1.0 >>> >>> sipx-openfire-3.6.4-3 >>> >>> As you can see, there is considerable potential for confusion. I think >>> we need to revise our naming conventions to avoid having, e.g., two RPMs >>> whose basic names differ only by a hyphen. What would be a better >>> scheme? >> >> Perhaps when we create an rpm by building outside package foo, we should >> name it something like sipximport-foo, and then any additions to it from >> our own code base can be sipx-foo-<something-descriptive> > > How about: > > For RPMs which are strictly a repackaging of outside packages: > sipximport-[package-name] > > For RPMs which are our additions to outside packages: > sipx[package-name]-[something-descriptive] > > (Which is what you suggested, with the removal of a single hyphen.) > > That way "sipximport" is a sipXecs pseudo-component which contains all > the imported packages, and each imported package has a sipXecs component > sipx[package-name] which contains all of our additions to it. (And > sipx[package-name] will be the top-level directory in which the > additions are built.) > > That produces the following RPM names: > > sipxfreeswitch-4.1.0 > > becomes --> sipxfreeswitch-plugin-4.1.0 > > sipx-freeswitch-1.0.4 > sipx-freeswitch-codec-passthru-amr-1.0.4 > sipx-freeswitch-codec-passthru-g723_1-1.0.4 > sipx-freeswitch-codec-passthru-g729-1.0.4 > sipx-freeswitch-devel-1.0.4 > sipx-freeswitch-lang-en-1.0.4 > sipx-freeswitch-lua-1.0.4 > sipx-freeswitch-perl-1.0.4 > sipx-freeswitch-spidermonkey-1.0.4 > > --> sipximport-freeswitch-1.0.4 > sipximport-freeswitch-codec-passthru-amr-1.0.4 > sipximport-freeswitch-codec-passthru-g723_1-1.0.4 > sipximport-freeswitch-codec-passthru-g729-1.0.4 > sipximport-freeswitch-devel-1.0.4 > sipximport-freeswitch-lang-en-1.0.4 > sipximport-freeswitch-lua-1.0.4 > sipximport-freeswitch-perl-1.0.4 > sipximport-freeswitch-spidermonkey-1.0.4 > > sipxopenfire-4.1.0 > > --> sipxopenfire-plugin-4.1.0 > > sipx-openfire-3.6.4-3 > > --> sipximport-openfire-3.6.4-3 > > Dale >
-1 The current naming scheme is consistent and well established, as a result of being being utilized in several product releases. Attempting to make the proposed change in order to address such a trivial complaint does not warrant the excessive amount of work and testing that would be involved. I am certain that there are many other tasks that people could be investing time in that would yield far more value to the product. -Mardy
_______________________________________________ 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/
