谁能帮忙翻译一下有关svn安装方面的文章.(3)

szhu · 发表于 2006-11-3 10:38:20

2.  autoconf 2.50 or newer (Unix only)

   This is required only if you plan to build from the latest source
   (see section II.B). Generally only developers would be doing this.

   3.  libtool 1.4 or newer (Unix only)

   This is required only if you plan to build from the latest source
   (see section II.B).

   Note: Some systems (Solaris, for example) require libtool 1.4.3 or
   newer. The autogen.sh script knows about that.

   4.  Neon library 0.25 or 0.26 (http://www.webdav.org/neon/)

   The Neon library allows a Subversion client to interact with remote
   repositories over the Internet via a WebDAV based protocol.  If you
   want to use Subversion to connect to a server over ra_dav (via a
   http:// or https:// url), you will require Neon.  (See also section
   I.11 for information about "serf", an experimental alternative to
   Neon for accessing servers over WebDAV.)

   The source code is included with the Subversion dependencies package,
   and it can also be obtained from:

      http://www.webdav.org/neon/neon-0.25.5.tar.gz
      http://www.webdav.org/neon/neon-0.26.1.tar.gz

   Building Neon inside the subversion build:

   The Neon library source code can be placed in "./neon" if you
   want Subversion to build it as part of the Subversion build process.

   Unpack the archive using tar/gunzip.  Rename the resulting
   directory from ./neon-0.XX.Y to just "./neon", inside the top
   level of your Subversion source tree.  (This is what unpacking the
   Subversion dependencies package does, too.)

   Using Neon as an external library:

   We recommend that you keep the neon installation out of the
   Subversion working copy.  This is because most developers have
   multiple working copies of Subversion, and it is easier to use a
   single instance of the Neon library for all instances.  To do
   this, just unzip/untar Neon, and build and install it according
   to its own standard installation instructions.  Then follow the
   steps below to use the installed Neon when building

   Subversion's configuration mechanism should auto-detect the
   installed Neon.  If it does not, you may need to set the LDFLAGS
   environment variable when you run "./configure", or specify
   Neon's location by passing the "--with-neon=" option to
   "./configure".  Look for the "neon-config" script in a "bin/"
   subdirectory of the target of "--with-neon".  For example, if
   you pass "--with-neon=/usr/local/myneon/", then there should be
   a file "/usr/local/myneon/bin/neon-config".

   5.  Berkeley DB 4.X

   Berkeley DB is needed to build a Subversion server that supports
   the bdb repository filesystem, or to access a bdb repository on
   local disk.  If you will only use the fsfs repository filesystem,
   or if you are building a Subversion client that will only speak
   to remote (networked) repositories, you don't need it.

   The current recommended version is 4.3.27. We *strongly* recommend
   using 4.3 or 4.2 over 4.1 or 4.0.  Not only are these the fastest
   and most stable we've seen, but they also enable Subversion
   repositories to automatically clean up database journal files to
   save disk space.

   You'll need Berkeley DB installed on your system.  You can
   get it from:

      http://www.sleepycat.com/download/index.shtml

   If you have Berkeley DB installed in a place not searched by default
   for includes and libraries, add something like this:

      --with-berkeley-db=/usr/local/BerkeleyDB.4.3

   to your `configure' switches, and the build process will use the
   Berkeley library in the named directory.  You may need to use a
   different path, of course.  Note that in order for the detection
   to succeed, the dynamic linker must be able to find the libraries
   at configure time.

   If you are on the Windows platform and want to build Subversion,
   a precompiled version of the Berkeley DB library is available for
   download at the Subversion web site "Documents & files" area:

      http://subversion.tigris.org/servlets/ProjectDocumentList

   Look in the "Releases > Windows > Windows BDB" section.

   6.  Apache Web Server 2.0.49 or newer
      (http://httpd.apache.org/download.cgi)

   The Apache httpd server is one of two methods to make your Subversion
   repository available over a network - the other is a custom server
   program called svnserve, which requires no extra software packages.
   Building Subversion, the Apache server, and the modules that Apache
   needs to communicate with Subversion are complicated enough that there
   is a whole section at the end of this document that describes how it
   is done: See section III for details.

   6.1 Apache Web Server 2.0.54 or newer (Windows only)
      (http://httpd.apache.org/download.cgi)

   If you are on Windows, you will need at least version 2.0.54 of
   the Apache Web server. Earlier versions don't support file locking,
   which was introduced in Subversion 1.2.

   7.  Python 2.0 (http://www.python.org/)

   If you want to run "make check" or build from the latest source
   under Unix as described in section II.B and III.D, install
   Python 2.0 or higher on your system. The majority of the test
   suite is written in Python, as is part of Subversion's build
   system.  Note that compiling under Windows requires Python 2.2
   or newer.

   8.  Visual C++ 6.0 or newer (Windows Only)

   To build Subversion under any of the MS Windows platforms, you
   will need a copy of Microsoft Visual C++.  You can generate the
   project files using the gen-make.py script.

   9. Perl 5.8 or newer (Windows only)

   To build Subversion under any of the MS Windows platforms, you
   will also need Perl 5.8 or newer to run apr-util's w32locatedb.pl
   script.

   10. MASM 6 or newer (Windows only, optional)

   The Windows build scripts for Subversion can use the Microsoft
   Macro Assembler (MASM) to build an optimized version of the ZLib
   library. Make sure that the version of MASM you use is compatible
   with the C compiler. If you're using MSVC 6, and don't have MASM 6,
   a free MASM-compatible assembler is available here:

      http://www.masm32.org/

   You only need ML.EXE and ML.ERR from this distribution.

   The VS.NET installation already contains MASM (but note, that
   version if MASM is not compatible with MSVC 6).

[ 本帖最后由 szhu 于 2006-11-3 10:42 编辑 ]