[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Suggestion for SVN Documentation

From: Ryan Schmidt <subversion-2009a_at_ryandesign.com>
Date: Mon, 19 Jan 2009 18:03:08 -0600

On Jan 19, 2009, at 14:22, Rez wrote:

> 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.

Neon is a library for connecting to WebDAV servers. Subversion can
alternatively use Serf. So you need either Neon or Serf if you want
to connect to http or https repositories.

SWIG, the Simplified Wrapper and Interface Generator, creates the
Subversion language bindings for Python and other languages. So if
you need language bindings, for example if you want to install Trac,
then you need SWIG.

Book feedback is best sent to the book's mailing list. See the
heading "Feedback/Contributing" about halfway down this page:

http://www.svnbook.org/

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1036141

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-20 07:10:10 CET

This is an archived mail posted to the Subversion Users mailing list.