Home > Store

Subversion Version Control: Using the Subversion Version Control System in Development Projects

Register your product to gain access to bonus material or receive a coupon.

Subversion Version Control: Using the Subversion Version Control System in Development Projects


  • Sorry, this book is no longer in print.
Not for Sale


  • Copyright 2005
  • Edition: 1st
  • Book
  • ISBN-10: 0-13-185518-2
  • ISBN-13: 978-0-13-185518-2

In any software development project, many developers contribute changes over a period of time. Using a version control system to track and manage these changes is vital to the continued success of the project. This book introduces you to Subversion, a free, open-source version control system, which is both more powerful and much less complex than its predecessor CVS.

In this practical, hands-on guide, you will learn how to use Subversion and how to effectively merge a version control system within your development process. As a seasoned Subversion user, William Nagel draws on lessons learned through trial and error, providing useful tips for accomplishing tasks that arise in day-to-day software development. Nagel clearly explains how to expand on the built-in abilities of Subversion, making the system work better for you. He organizes Subversion commands by activity to allow for quick task reference. Using example scripts and configurations, he also includes development approaches that you can customize to fit your own environment.

Inside, you will find

  • A guide to installing Subversion on Linux, Windows, and Mac OS X.
  • A tutorial walkthrough of Subversion, from creating your first repository to basic branching and merging.
  • A detailed look at the most important Subversion client commands, as well as properties, user configuration, and integration with a variety of external tools.
  • A guide to repository administration and organization, including repository security and migration from another version control system.
  • An in-depth look at automation in Subversion, including using hook scripts, metadata, and the Subversion API, plus example scripts.
  • Case studies that examine both archetypal and real-world projects and their use of Subversion.
  • A Subversion command reference for fast access to essential technical information.
  • Details on Subversion's many advanced features, such as its Apache-integrated WebDAV server and database file storage system.

Whether you are an administrator, project manager, or software developer, Subversion Version Control will show you how to realize the full potential of Subversion.



Untitled Document Download Subversion Version Control in PDF

Sample Content

Online Sample Chapter

Introduction to Subversion, an Open Source Version Control Tool

Downloadable Sample Chapter

Untitled Document Download the Sample Chapter related to this title.

Table of Contents

Preface xvii
Acknowledgments xxi

Part I: An Introduction to Version Control and Subversion 1

Chapter 1: An Introduction to Version Control 3

1.1 What Is Version Control? 4

1.2 Why Use It? 4

1.3 The Elements of Version Control 7

1.4 Summary 12

Chapter 2: An Introduction to Subversion 15

2.1 Why Subversion? 15

2.2 Limitations of Subversion 21

2.3 Summary 23

Chapter 3: Installing Subversion 25

3.1 Installing on Linux 25

3.2 Installing on Mac OS X 29

3.3 Installing on Windows 30

3.4 Configuring SVN to Use Apache 31

3.5 Configuring to Use Svnserve 34

3.6 Summary 36

Chapter 4: Basic Subversion Usage 37

4.1 Creating the Repository 37

4.2 Getting Files into the Repository 38

4.3 Creating a Working Copy 40

4.4 Editing Files 40

4.5 Committing Changes 42

4.6 Viewing the Logs 42

4.7 Creating a Tag 43

4.8 Creating a Branch 44

4.9 Merging a Branch 46

4.10 Handling Conflicts 48

4.11 Summary 51

Part II: Subversion from a Client User's Perspective 53

Chapter 5: Working with a Working Copy 55

5.1 The Subversion Client 55

5.2 Checking Out and Maintaining a Working Copy 57

5.3 Modifying and Committing Data 61

5.4 Getting Information about the Repository 67

5.5 Changing the Working Copy Target 76

5.6 Resolving Conflicts 76

5.7 Branching, Tagging, and Merging 78

5.8 Troubleshooting the Working Copy 82

5.9 Summary 83

Chapter 6: Using Properties 85

6.1 Storing Metadata 85

6.2 Retrieving Metadata 87

6.3 Built-in Properties 90

6.4 Summary 96

Chapter 7: Configuring the Client 97

7.1 Finding the Configuration Files 97

7.2 Editing the Configuration Files 97

7.3 Summary 104

Chapter 8: Integrating with Other Tools 105

8.1 Accessing SVN through a GUI Client 105

8.2 Accessing Directly from an IDE 111

8.3 Using Autoversioning with WebDAV 114

8.4 Summary 116

Part III: Subversion from an Administrator's Perspective 117

Chapter 9: Organizing Your Repository 119

9.1 Laying Out the Repository 119

9.2 Planning for Growth 126

9.3 Migrating an Existing Repository 129

9.4 Summary 136

Chapter 10: Administrating the Repository 137

10.1 Controlling Access to the Repository 137

10.2 Backing Up the Repository 149

10.3 Unwedging Your Repository 154

10.4 Upgrading Subversion 156

10.5 Summary 156

Chapter 11: The Joy of Automation 159

11.1 An Introduction to Hooks 160

11.2 Making the Most of Hook Scripts 167

11.3 Taking Advantage of Metadata 191

11.4 The Subversion API 198

11.5 Summary 206

Part IV: The Software Development Process 207

Chapter 12: Development Process Policies 209

12.1 Effective Branching and Tagging 209

12.2 Checking In Code 217

12.3 Log Data 219

12.4 Project Builds 223

12.5 Testing and Quality Assurance 227

12.6 Communication 230

12.7 Enforcing Policies 232

12.8 Summary 233

Chapter 13: Integrating SVN with the Development Process 235

13.1 SVN in Different Developers' Workflows 235

13.2 Using SVN in Peer Reviews 240

13.3 Tying Revisions to Issue Tracking 246

13.4 Summary 249

Chapter 14: Case Studies in Development Processes 251

14.1 Archetypal Studies 251

14.2 Real-world Studies 260

Part V: Reference 271

Chapter 15: Command Reference 273

15.1 svn 273

15.2 svnadmin 308

15.3 svnlook 314

15.4 svnversion 320

15.5 svndumpfilter 321

Index 325


Untitled Document

I was first introduced to version control (and CVS) in college, about the same time I was introduced to Linux. At that time though, most of the projects I worked on were small and generally involved only a couple of developers. So, although version control would have been useful, I never took the time to really use it; my knowledge of CVS remained limited to what little I needed to know to check out the occasional bleeding-edge project on Linux (which seemed necessary a little more often in those days). As my college career progressed, the projects I worked on became more involved, and I began to learn about "software engineering." The instruction I received on software engineering never really covered version control in any depth though, and despite the increased size of the software projects I was working on, I never delved into using a version control system to keep track of things. I wanted to; I thought CVS was a neat idea. I just never invested the timenecessary to learn how to set it up and use it. Then came my first major team project. It was a real-world project, with real-world clients, and its completion was required for graduation. Finally, I had an excuse to really give version control a try. I presented the case for CVS to my teammates and (although there was some small resistance) convinced them that we needed to use it. It was a success. By the end of the project, I was fully sold on the necessity of version control in any future projects, however big or small. I loved CVS.

After school came the real world, and the love affair with CVS didn't last long. As I learned (mostly through trial and error) how version control systems should be used, CVS steadily became more and more inadequate. I could see its potential, but it didn't measure up. Code was lost, fits were thrown, and hair was pulled. Still, CVS was the best free, open source version control system out there, and as an entrepreneur trying to keep a start-up company going, free was a required feature. Then someone told me about a new versioncontrol project called Subversion, so I went to its site and took a look. It seemed intriguing, but it wasn't quite up to the point where I could trust it for my code--and I barely had time to eat back then, so getting involved in the project's development was out of the question. Instead, Subversion went on my back burner and I moved on to other things.

Several months down the road, I saw that Subversion had become self-hosting. "Well," I thought, "If they trust it with their own code, maybe it's time to take another look." Rolling up my sleeves, I sat down to play around with it. Once again, I had fallen in love. Subversion was everything CVS could have been. It was stable, it was flexible, and it didn't eat my code. Thus, after a suitable period of testing, CVS was unceremoniously chucked and replaced by Subversion. I've never regretted the change. In fact, the only thing regrettable is the hours of my life wasted fighting with CVS.

Writing the Book

When I was first approached about writing a book on Subversion, my first thought was, "Why?" There's already an excellent Subversion manual, written by several of the principle Subversion authors (who presumably know more about Subversion's inner workings than I do), and it's freely available at that. So, I almost turned down the opportunity to write this book because I couldn't imagine why anyone would want to read it. What could I possibly add that wasn't already written? Then I got to thinking back to my college days, when I learned version control through trial and error (mostly error). I had the manual to CVS, but it covered how to use CVS, not how to use version control. It was a good manual, it just wasn't complete. The Subversion manual is similar; although it is far, far better than the documentation available for CVS, it's still primarily a technical manual. As a technical manual, it is excellent. As a guide to realizing Subversion's full potential in relation to your software development project, it isn't complete. Therefore, I've written this book to be theguide I never had when I was learning how to use version control.

Of course, this book aims to cover the nuts and bolts of Subversion as completely as possible--you can't very well use Subversion to develop software if you can't use Subversion--but it does so in the context of how to do the things you want to do in dayto-day software development. The book also goes a step further: It explains how to expand on the built-in capabilities of Subversion to make the system work for you. In some places, that takes the form of example scripts or configurations. In others, it is merely ideas that you can expand to fit your software development process. This is not a book to sell a process. I do make suggestions here and there of what I think will work in certain situations, but you don't need to buy into my "exhalted process" to get the most from this book. Instead of showing you how you should develop your software, I show you how Subversion can make your process easier.

The Layout of the Book

The book is split into five sections, each covering Subversion from a different perspective.

Part I: An Introduction to Version Control and Subversion

This first part looks at Subversion from the beginner's perspective. It explains what version control is, why it is useful, and how Subversion fits into the version control world. It shows you how to install and set up Subversion, and it walks you through Subversion's essential features.

Chapter 1 An introduction to the essential concepts that make up a version control system.

Chapter 2 An introduction to Subversion's features and how they compare to some other common version control systems.

Chapter 3 A basic guide to installing Subversion on Linux, Windows, and Mac OS X.

Chapter 4 A tutorial walkthrough of Subversion, from creating your first repository to basic branching and merging.

Part II: Subversion from a Client User's Perspective

The second part of the book examines Subversion from the perspective of the client user. It takes a detailed look at using the most important Subversion client commands, as well as properties, user configuration, and integration with a variety of external tools.

Chapter 5 Walk through a Subversion working copy and the commands used to interact with it. Most of the common Subversion client commands are covered in this chapter.

Chapter 6 How to use the Subversion tools to work with properties attached to versioned files.

Chapter 7 A look at Subversion client configuration and customization for an individual work environment.

Chapter 8 An overview of many of the client tools that Subversion can integrate and interact with.

Part III: Subversion from an Administrator's Perspective

This is a look at Subversion from the admin's perspective. In this section, I talk about repository administration and organization. I show how to use automation to help integrate Subversion into your development process, and I examine the nuts and bolts of such things as repository security and migration from another version control system.

Chapter 9 Tips on repository organization, as well as how to migrate an old repository to Subversion with minimal loss of history and metadata.

Chapter 10 Basic repository administration: security, backup, and repository maintenance.

Chapter 11 An in-depth look at automation in Subversion, using hook scripts, metadata, and the Subversion API. Includes a number of example scripts that you can use in your project.

Part IV: The Software Development Process

This part takes a look at Subversion from the project manager's perspective. It looks at the software development process and how Subversion can fit into a variety of different types of projects, with many different policies and philosophies.

Chapter 12 An overview of different policies adopted by many development projects and how Subversion can be used to complement those policies.

Chapter 13 An examination of the software development process and how Subversion can be integrated into that process.

Chapter 14 Case studies that examine both archetypal and real-world projects and their use of Subversion.

Part V: Reference

The final section is a Subversion command reference. When you need to look up something quickly, it can be difficult to sift through paragraphs of expositional language. This section takes the essential technical information from the Subversion commands and makes it easy to find quickly.


Untitled Document Download the Index related to this title.


Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020