When you addpkg a package to your private release you are in fact simply performing a `cvs checkout` for that package (see section on CVS for more details). Thus after modifying a package you can commit your changes back to the repository.

Before comiting modifications to a B A B A R package you should:

Always check that your changes actually work.
Check with the coordinator for the package in question.

Some packages may not actually allow all users to commit changes directly. This restriction is at the discretion of the package coordinator.

To commit your modifications to e.g. gnemca:

cvs update -A gnemca
cvs commit gnemca -m "<comment on why and when>"

The `cvs update` brings the version of the package which you have up to date. If you have an old version then it is possible that several other modifications have already been made to the repository (see section on CVS). It is up to you to resolve any conflicts before performing the commit. The -A option is required to bring the (CVS) tags associated with your copy of the package up to date. Otherwise you will get a meesage something like:

cvs commit: sticky tag 'HEAD' for file 'dswrite.F' is not a branch

when you try to update or commit.

Next: Updating a Test Release Up: Using SRT Previous: Using SRT

Neil I. Geddes
1998-11-18