I have a few suggestions and not sure if this is the right forum to post it in or whether it should be posted or addressed to those who maintain the documentation for Subversion. I would love to see either another chapter or an appendix added to the book outlining the migration process from other version control software, such as CVS, instead of, making a vague reference to cvs2svn in the current document's appendix B on page 349.
Currently the way the documentation is written, a new Admin has to practically read almost the entire documentation, generate their own crib notes, roll up their sleeves, and go at it. I think it would really help novices like me, to see a chapter outlining the general steps before preceding to chapters 5 & 6.
Would love to see outlines and then a chapter or subsection expanding on each enumerated item:
1. Prepare new server (detail and specs of the server not the scope of this manual).
2. Install subversion, mod_dav_svn, neon, swig, apache 2.0, and oldRepo2newRepo converter (e.g. cvs2svn) on the new machine.
3. Tarball old repository, e.g. CVS. And move tarball to the new SVN server and run converter.
4. Configure httpd.conf or configure protocol of choice and set up permissions and users.
5. Configure SVN hook scripts.
6. On the client machine, e.g. Windows, download GUI, configure, and do a check out.
BTW, are Neon and Swig still necessary and part of the installation? The documentation doesn't explain what they're and their website give a vague explanation as to what they're. Many thanks to the folks who write and maintain the documentation, it's really great help to many of us.
Windows Live™: Keep your life in sync.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-19 21:28:27 CET