Книга: Fedora™ Unleashed, 2008 edition

Managing Software Projects with Subversion

Managing Software Projects with Subversion

Although make can be used to manage a software project, larger software projects require document management, source code controls, security, and revision tracking as the source code goes through a series of changes during its development. Subversion provides source code version control utilities for this kind of large software project management.

The Subversion system is used to track changes to multiple versions of files, and it can be used to backtrack or branch off versions of documents inside the scope of a project. It can also be used to prevent or resolve conflicting entries or changes made to source code files by multiple developers. Source code control with Subversion requires the use of at least the following five command options on the svn command line:

? checkout — Checks out revisions

? update — Updates your sources with changes made by other developers

? add — Adds new files to the repository

? delete — Eliminates files from the repository

? commit — Publishes changes to other repository developers

Note that some of these commands require you to use additional fields, such as the names of files. With the commit command, you should always try to pass the -m parameter (lets you provide a message describing the change) followed by some information about your changes. For example:

svn commit -m "This fixes bug 204982."

One of the most impressive features of Subversion is its ability to work offline — any local Subversion checkout automatically has a .svn directory hidden in there, which contains copies of all checked out files. Thanks to this, you can check your current files against the ones you checked out without having to contact the server — it all runs locally.

Оглавление книги