CVS---Concurrent Versions System. Node: Tracking sources

PREVKeyword substitution UPTop NEXTBuilds

Chapter 13: Tracking third-party sources

If you modify a program to better fit your site, you probably want to include your modifications when the next release of the program arrives. CVS can help you with this task.

In the terminology used in CVS, the supplier of the program is called a vendor. The unmodified distribution from the vendor is checked in on its own branch, the vendor branch. CVS reserves branch 1.1.1 for this use.

When you modify the source and commit it, your revision will end up on the main trunk. When a new release is made by the vendor, you commit it on the vendor branch and copy the modifications onto the main trunk.

Use the import command to create and update the vendor branch. When you import a new file, the vendor branch is made the `head' revision, so anyone that checks out a copy of the file gets that revision. When a local modification is committed it is placed on the main trunk, and made the `head' revision.

  • First import Importing a module for the first time
  • Update imports Updating a module with the import command
  • Reverting local changes Reverting a module to the latest vendor release
  • Binary files in imports Binary files require special handling
  • Keywords in imports Keyword substitution might be undesirable
  • Multiple vendor branches What if you get sources from several places?
  • PREVKeyword substitution UPTop NEXTBuilds