- Taschenbuch: 336 Seiten
- Verlag: O'Reilly & Associates; Auflage: 1 (20. Juni 2003)
- Sprache: Englisch
- ISBN-10: 0596004591
- ISBN-13: 978-0596004590
- Größe und/oder Gewicht: 17,8 x 2,2 x 23,3 cm
- Durchschnittliche Kundenbewertung: 1 Kundenrezension
- Amazon Bestseller-Rang: Nr. 1.108.371 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
- Komplettes Inhaltsverzeichnis ansehen
Essential CVS (Englisch) Taschenbuch – 20. Juni 2003
|Neu ab||Gebraucht ab|
Dieses Buch gibt es in einer neuen Auflage:
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
"Essential CVS does what you might think would be a small job more effectively and more comprehensively than I would have imagined, even allowing for the generally high standard of O'Reilly books. Apart from covering the boring stuff well, it has two big advantages over the Web: it backs up its discussion of various CVS functions with wise advice and policies on why and how to use these facilities - plus it provides readable (and, presumably, tested) examples. Computing sciences prizes abstraction and generalities; computing practice should, like this book, be informed by concrete specifics and sensible rules-of-thumb." - Damian Counsell, news@UK, December 2003
CVS, the Concurrent Versions System, is the popular source-code management tool that frees developers from the chaos that too often ensues when multiple users work on the same file. An open source technology that is available on most computer platforms, including Windows and Mac OS X, CVS is widely used to manage program code, Web site content, and to track changes made to system configuration files. Multiple users can check out files from a directory tree, make changes, and then commit those changes back into the directory. If two developers modify the same file, CVS enables both sets of changes to be merged together into one final file. This text is a complete and easy-to-follow reference that helps programmers and system administrators apply order to the task of managing large quantities of documents. It covers basic concepts and usage of CVS, and features a comprehensive reference for CVS commands - including a handy Command Reference Card for quick, on-the-job checks. The book also includes advanced information on all aspects of CVS that involve automation, logging, branching and merging, and "watches."Readers will find in-depth coverage of the following: installing CVS and building your first repository; basic use of CVS, including importing projects, checking out projects, committing changes, and updating projects; tagging, branching and merging; working with multiple users; clients, operating systems, and IDEs; repository management and managing remote repositories; project administration, including bug tracking systems, enforcing log messages; and history and annotation. Version control is essential to maintaining order in any project, large or small. Any CVS user, from beginners to team leaders and system administrators, should find this practical guide to CVS indispensable in getting the most from this valuable tool. Alle Produktbeschreibungen
Die hilfreichsten Kundenrezensionen auf Amazon.com
Most of the things you'll do with CVS are covered in sufficient detail in this book. I do agree with the reviewer who mentioned this is not the perfect reference for some tasks - like merging branches. This book will, however, give you all the background information you'll need so that you can effectively research complex topics like this on the web. The title is appropriate - 'essential CVS.' It's not 'everything there is to know about CVS' - and that's a strength of the book. It makes it small enough that the average developer can read the 'quickstart,' and have a basic understanding of how things work. They can then use the more detailed chapters to gain further information. Only the CVS administrator will need a little more. Even for them, this book will be a handy reference.
I especially appreciate the author's discussion on tagging and branching strategies. She compares available branching strategies, talks about pros and cons of each in details to help you pick the one you see more fit.
She also provides tips and tricks, ranging from absurd (such as switching your sandbox by editing your CVS/Repository file) to intimidating (such as playing with the repositories directly). These tips will help you understand the system's internals, which hopefully will result in productivity (if not in disaster).
At first, I found her discussions a bit redundant - you can read the same point repeated several times on the same page or the same chapter over and over. Although it annoyed me to some extent, people not familiar with CVS may appreciate this feature of the book.
She assumes her audience to be familiar with UNIX systems. Although I'm fine with it (I live in Linux), others may not be. Most of the UNIX-related chat are found in her file-utility commands, as well as bash scripts, in addition to some user account/group management.
The organization and writing style of the book is far from ideal. CVS itself is a very exciting topic for software developers. The author of Essential CVS fails to reflect this in her discussions. Her discussions are close to manpage-style, with some detour onto tips and suggestions from time to time.
I believe ideal style for a book on CVS would be a scenario-driven style, which introduces a project, a problem related with managing it, and advances into the features of CVS one solution at a time. Realize, that is it different from cook-book style, which is a Question & Answer styled writing.
Good examples of scenario-driven styled writing are "Apache The Definitive Guide" by O'reilly, which builds a server with a tiny configuration file, and advances to more feature-ful implementation; "MySQL" book of New Riders, which introduces a conventional grade book and advances into more complex RDBMS implementation of it; "DNS and BIND" of O'reilly and etc.
seem to assume that you implicitly understand all of
the jargon and lingo. I purchased this book hoping
that it would be a more gentle introduction into
CVS without assuming that I already understood all
of the terms. I was not impressed.
In the introduction of tagging, the author clearly explain
that cvs tag allows you to tag a revision of a file so
that you can use the tag name instead of the version number.
But what the auther doesnt explain is whether a file can have
multiple tags. Whether there is a limit to the number
of tags that file can have. How to find out what tags
are on a particular file. Whether you can tag an entire
directory and all of the files in it. Whether all of
the files in a directory have a particular tag or only some
The author explains that there are two special revisions
of BASE and HEAD. But there are few introductions on how
to determine what the BASE version is on a particular FILE,
nor how to determine what the HEAD version is. If you understand
these terms, then there is no need for documentation on
what these terms mean and how to use them. But if you dont understand
there is no gentle introduction with examples on how to examine, change,
or query how these apply to a particular file.
As an example, The author says that the tag command "tags file in the current sandbox".
Without an understanding, you might assume that it would not affect
the repository. If you understand tags, you understand how tagging affects
the repository. The author doesnt clearly lead you by the hand and show you.
Instead, like too many technical documents, they describe in a few
words how they might use it in a general case rather than giving several
As a book that is a technical reference for CVS for someone
that already understands CVS it is reasonable. For a book that is
used for teaching CVS as an intro to revision control and how to apply CVS
to your favorite developement effort, i found it somewhat somewhat
Ähnliche Artikel finden