Jerry: >> Some issues and concerns: >> >> - In spec-files-other we deliver SUNWlibpigment-python24, >> SUNWpython24-cssutils, SUNWpython24-simplejson, and SUNWpyyaml24. >> All of the other 2.4 bindings packages do not have "24" in the name. >> Wouldn't it be better to remove the "24" from these packages for >> consistency? Or add "24" to all Python 2.4 bindings? > Add 24 to all python 2.4 binding pkgs, > it will be easy to remove them batch.
On one hand, adding "24" to all Python 2.4 packages would make the package names look more consistent. However, this option may not be easy because most packages names are ARC'ed as "Uncommitted" and therefore cannot be changed without going through a round of ARC. Also, you run the risk of breaking things for people who might be depending on the package names. Some external users, for example, might have packages that depend on these package names. So, we really only have the freedom to easily change the naming for packages which have not yet delivered in a product yet. In other words, only new modules that have not yet shipped in an OpenSolaris product (e.g. CSSutils, simplejson, and pyyaml can easily be renamed). However, we will lose the ability to rename them after the next release of OpenSolaris. So, we currently have a standard where the Python 2.4 modules are in packages without "24" in the name. Shouldn't we stick to this standard? Or do we want a mix-mash of packages with different naming? >> - Most Python packages are named SUNWpython-foo. However, some >> packages don't follow this: SUNWlibpigment-python, >> SUNWmysql-python, SUNWpyyaml, SUNWsexy-python, >> SUNWcompizconfig-python, SUNWgst-python, SUNWpysqlite, and >> SUNWgnome-python-libs. Might it be better to follow more >> consistent naming? At least for new packages which are going >> into the next OpenSolaris release (pigment, and pyyaml). >> > I suggest to use ***-python You are suggesting this for what? As I said, most Python packages are named SUNWpython-*. Are you suggesting we rename all packages to move "python" to the end of the package name? This might not be the best suggestion since, as I said before, we can not easily change package names for packages which have already shipped in a release. Brian
