51Testing软件测试论坛

标题: 谁能帮忙翻译一下有关svn安装方面的文章.(7) [打印本页]

作者: szhu 时间: 2006-11-3 10:57
标题: 谁能帮忙翻译一下有关svn安装方面的文章.(7)
Then build subversion:

C:>msdev subversion_msvc.dsw /USEENV /MAKE "__ALL_TESTS__ - Win32 Release"
C:>cd ..

Or, with Visual C++.NET 2002, 2003, 2005:

C:>devenv subversion_vcnet.sln /build "Release" /project "__ALL_TESTS__"
C:>cd ..

Or, with Visual C++ Express 2005:

C:>msbuild subversion_vcnet.sln /t:__ALL_TESTS__ /p:Configuration=Release
C:>cd ..

The binaries have now been built.

E.5 Packaging the binaries

You now need to copy the binaries ready to make the release zip
file. You also need to do this to run the tests as the new binaries
need to be in your path. You can use the build/win32/make_dist.py
script in the Subversion source directory to do that.

[TBD: Describe how to do this. Note dependencies on zip, jar, doxygen.]

E.6 Testing the Binaries
[TBD: It's been a long, long while since it was necessary to move
      binaries around for testing. win-tests.py does that automagically.
      Fix this section accordingly, and probably reorder, putting
      the packaging at the end.]

The build process creates the binary test programs but it does not
copy the client tests into the release test area.

C:>cd src-%DIR%
C:>mkdir Release\subversion\tests\cmdline
C:>xcopy /S /Y subversion\tests\cmdline Release\subversion\tests\cmdline

If the server dso modules  have been built then copy the dso files and
dlls into the Apache modules directory.

C:>copy Release\subversion\mod_dav_svn\mod_dav_svn.so "%APACHEDIR%"\modules
C:>copy Release\subversion\mod_authz_svn\mod_authz_svn.so
   "%APACHEDIR%"\modules
C:>copy svn-win32-%VER%\bin\intl.dll "%APACHEDIR%\bin"
C:>copy svn-win32-%VER%\bin\iconv.dll "%APACHEDIR%\bin"
C:>copy svn-win32-%VER%\bin\libdb42.dll "%APACHEDIR%\bin"
C:>cd ..

Put the svn-win32-trunk\bin directory at the start of your path so
you run the newly built binaries and not another version you might
have installed.

Then run the client tests:

C:>PATH=%DRIVE%:\SVN\svn-win32-%VER%\bin;%PATH%
C:>cd src-%DIR%
C:>python win-tests.py -c -r -v

If the server dso modules were built configure Apache to use the
mod_dav_svn and mod_authz_svn modules by making sure these lines appear
uncommented in httpd.conf:

   LoadModule dav_module       modules/mod_dav.so
   LoadModule dav_fs_module    modules/mod_dav_fs.so
   LoadModule dav_svn_module    modules/mod_dav_svn.so
   LoadModule authz_svn_module modules/mod_authz_svn.so

And further down the file add location directives to point to the
test repositories. Change the paths to the SVN directory you created
(paths should be on one line even if wrapped here):

   <Location /svn-test-work/repositories>
   DAV svn
   SVNParentPath C:/SVN/src-trunk/Release/subversion/tests/cmdline/
                  svn-test-work/repositories
   </Location>

   <Location /svn-test-work/local_tmp/repos>
   DAV svn
   SVNPath c:/SVN/src-trunk/Release/subversion/tests/cmdline/
            svn-test-work/local_tmp/repos
   </Location>

Then restart Apache and run the tests:

C:>python win-tests.py -c -r -v -u http://localhost
C:>cd ..

III.  BUILDING A SUBVERSION SERVER
   ============================

  A.  Setting Up Apache
   -----------------

   (Following the BOOTSTRAPPING FROM RPM procedures above will install and
   build the latest Subversion server for Linux RedHat 7.1, 7.2, and PPC
   Linux systems *IF* the apache-devel-2.0.41 or greater package is already
   installed when the SUBVERSION RPM is built.)

   1.  Obtaining and Installing Apache 2.0

   Subversion tries to compile against the latest released version
   of Apache httpd-2.0.  The easiest thing for you to do is
   download a source tarball of the latest release and unpack that.

   Alternately, if you'd rather use the latest SVN versions of
   everything, checkout the "httpd 2.0.x"  branch from apache.org.
   If you have questions about the Apache httpd 2.0 build, please consult
   the httpd install documentation:

      http://httpd.apache.org/docs-2.0/install.html

   Place this module wherever you wish; it's an independent project.

   $ svn co \
      http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x httpd-2.0

   Checkout the "apr" and "apr-util" modules into the srclib/ directory:

   $ cd httpd-2.0/srclib
   $ svn co \
      http://svn.apache.org/repos/asf/apr/apr/branches/0.9.x apr
   $ svn co \
      http://svn.apache.org/repos/asf/apr/apr-util/branches/0.9.x apr-util

   At the top of the httpd-2.0 tree:

      $ ./buildconf
      $ ./configure --enable-dav --enable-so --enable-maintainer-mode

   The first arg says to build mod_dav.

   The second arg says to enable shared module support which is needed
   for a typical compile of mod_dav_svn (see below).

   The third arg says to include debugging information.  If you
   built Subversion with --enable-maintainer-mode, then you should
   do the same for Apache; there can be problems if one was
   compiled with debugging and the other without.

   Note: if you have multiple db versions installed on your system,
   Apache might link to a different one than Subversion, causing
   failures when accessing the repository through Apache.  To prevent
   this from happening, you have to tell Apache which db version to
   use and where to find db.  Add --with-dbm=db4 and
   --with-berkeley-db=/usr/local/BerkeleyDB.4.2 to the configure
   line.  Make sure this is the same db as the one Subversion uses.
   This note assumes you have installed Berkeley DB 4.2.52
   at its default locations.  For more info about the db requirement,
   see section I.5.

   You may also want to include other modules in your build. Add
   --enable-ssl to turn on SSL support, and --enable-deflate to turn on
   compression support, for example.  Consult the Apache documentation
   for more details.

   All instructions below assume you configured Apache to install
   in its default location, /usr/local/apache2/; substitute
   appropriately if you chose some other location.

   Compile and install apache:

      $ make && make install

欢迎光临 51Testing软件测试论坛 (http://bbs.51testing.com/)