To put a new version of a package in the production area

The developer changes a package and communicates those changes to the package librarian. The librarian then commits the changes to the CVS repository. When the package librarian decides that it's time to make a new official version of the package, the librarian tags the consistent set of files that form the package with a unique CVS tag via the command cvs rtag <version> <package>. Once the version of the package has been tagged in the CVS repository, then:

• cd $SRT_DIST/packages/<package name>
• newver -p <cvs tag name>
  This creates the new version of the package in the official packages tree. The <cvs tag name> is the package version number, and has the format Vxx-xx-xx, where x is between 0 and 9. The area you are in, $SRT_DIST/packages/<package name>, provides the name of the package for the newver command. The ``-p'' option is currently required, and indicates this is a production version, so the files will be write-protected and have their timestamps updated. newver also declares this version of the product to the ups database.