Open Source Development with CVS (Paperback)

~ Moshe Bar (Author), Karl Franz Fogel (Author), (Author) "Traditional capitalism is based on the idea of limited supply; however, information has become a commodity in itself and is never in short supply..." (more)
Key Phrases: retrieving revision, first log message, temporary watcher, Sticky Options, Up-to-date Working, Sun Apr (more...)

Editorial Reviews

Amazon.com Review

The need for a modern source-code management strategy in the distributed open-source community is paramount. The benevolent dictatorship model of open-source maintainers is only quasi-stable, but it is far better than the other extreme: the chaos of democratic code development.

The best available compromise is the concurrent versioning system (CVS), which introduces proctored code merging into source code management. CVS is ideally suited for worldwide open-source development, and the world is ready for monographs that address the management issues that Per Cederqvist explicitly avoided in his fine 164-page postscript manual distributed with the CVS tar-ball. What is the role of a maintainer/manager in establishing test protocols for code merges? What minimal functional level of developer communications is necessary for merges to remain stable? Is a maintainer-less release possible?

These questions go largely unanswered in Karl Fogel's new Open Source Development with CVS. Fogel's 300-page book consists of chapters alternating between CVS basics and common code maintenance issues. He includes a few anecdotes from open-source lore and lots of nonspecific commonsense guidelines on team software development.

Fogel is at his best when he is engaging us in thinking about what should and should not be under CVS control. He points out that complex relationships exist between developing code and its dependencies on intimately related applications, such as build tools themselves (gcc, autoconf) or partner applications (e.g., the server's client or the client's server). His brief discussion of strategies is too short to be satisfying.

Frustratingly, this book is chock-full of postmodern self-indulgences, such as his boasting reverence for technological ignorance. The discipline needed by good maintainers is missing here; Fogel's informal prose is often grating, and his copious parenthetical remarks are distracting or bullying (they sure are); one wonders where his editor was. Ultimately, his management arguments boil down to an endorsement for the benevolent dictatorship model--a safe conclusion, but one that seems not to use CVS's merging capability for all it's worth. To the question of how to run a project, he responds, "Well, we're all still trying to figure that out, actually." True, and he isn't there yet, but at least he has the questions right. --Peter Leopold --This text refers to an out of print or unavailable edition of this title.

Product Description

The popular first edition was one of the first books available on development and implementation of open source software using CVS. Examining how CVS affects the architecture and design of applications, this third edition has been enhanced with more value-added material covering strategies, third-party tools, scalability, client access limits, and overall server administration for CVS.

See all Editorial Reviews

Product Details

• Paperback: 420 pages
• Publisher: Paraglyph Press; 3 edition (August 2003)
• Language: English
• ISBN-10: 1932111816
• ISBN-13: 978-1932111811
• Product Dimensions: 8.9 x 7.1 x 0.7 inches
• Shipping Weight: 1.2 pounds
• Average Customer Review: 4.3 out of 5 stars  See all reviews (29 customer reviews)
• Amazon.com Sales Rank: #1,015,139 in Books (See Bestsellers in Books)

Customer Reviews

Most Helpful Customer Reviews

17 of 17 people found the following review helpful:

5.0 out of 5 stars Great Book, December 5, 1999

By	R. Hiller (NJ, USA) - See all my reviews (REAL NAME)

This review is from: Open Source Development with CVS: Learn How to Work With Open Source Software (Paperback)

I've been using CVS for a couple of years, read the manual and had great success. However, there have been lots of gaps in my understanding and places where I wasn't really sure what was happenning. This book answered those. It has lots of well chosen examples that illustrate points that I've wondered about, but been afraid to try out for fear of really messing up my CVS repository.

The book is a little heavy on the "Open Source" religion, but dismissing it because of that would be a big mistake. This is a fine book.

15 of 15 people found the following review helpful:

4.0 out of 5 stars excellent, invaluable, not enough about permissions, August 20, 2001

By	Robert Nagle "idiotprogrammer" (Houston, TX United States) - See all my reviews (REAL NAME)

This review is from: Open Source Development with CVS: Learn How to Work With Open Source Software (Paperback)

Open Source Development with CVS Karl Fogel

Here is a chatty discussion of CVS and how to use it. The best thing about the book is that he spends a lot of time discussing his examples. That helps you to understand the output. I also found the troubeshooting section to be more than adequate, and a discussion of pcl-cvs (the plugin to emacs) to be a nice and helpful addition.

Fogel wrote some chapters about open source development. Call them filler or distractions, still it gives insight about how version control management contributes to open source. . The book has an appendix of descriptions of each command and at times Fogel urges the reader to refer to the Cederqvist manual. I actually appreciated that because it allowed Fogel to write about the things not already found in the online manual.

One quibble was with the organization of the book. To learn how to setup CVS from scratch, you need to start by reading chapter 4 (Admin), and then go back and reread chapter 2 (An overview). Maybe a briefer overview would have been better and an explanation of the functions in succeeding chapters.

The chattiness of the chapters (which is a good thing) often made it hard to find the user commands. Perhaps user input could have been highlighted in some way. Also, the discussion of file permissions was simply inadequate. Indeed, chapter 4 contained an error related to permissions on page 112 (what does "+R" mean? ) and didn't discuss sticky bits for group ownership. This was significant, because I couldn't proceed with learning CVS until I could figure out those permissions.

In short: an excellent, invaluable book, but you should consult the Cederqvist manual for the section of file permissions.

12 of 12 people found the following review helpful:

5.0 out of 5 stars Not only technical, but also community info..., February 28, 2001

By	John P. Hoke "Drinking at the Foo B@r" (Floral Park, NY United States) - See all my reviews (REAL NAME)

This review is from: Open Source Development with CVS: Learn How to Work With Open Source Software (Paperback)

I found this book a joy to read. Before ordering this book, I had read the GPL'd chapters online and found them to be quite good so I wanted to support the author with my wallet. I figgured the rest would be the regular pomp about Open Source that we are seeing alot of lately, but I could not have been more incorrect! The author not only knows his technical details about the CVS system, he fully groks the Open Source movement, personalities and community.

The author alternates chapters between community issues (ethics, forking, project maintenance and administration, as well as "people skills") and the technical nuts and bolts of running a CVS server and/or using a CVS client.

While the title touts the Open Source movement, CVS is just as at home in a closed environment, say a web development team, inhouse application development, or anywhere else that you need to track text based files. Mr. Fogel does a good job of showing run of the mill examples and code, as well as some more esoteric uses of CVS commands and utilities.

If you are doing any sort of development and are investigating content version control software this book (and application) are for you.