Sophie

Sophie

distrib > Mandriva > 2008.1 > x86_64 > by-pkgid > 0b38be552745286620faf2138b9468d0 > files > 77

subversion-doc-1.4.6-5.1mdv2008.1.x86_64.rpm

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Installing Subversion</title><link rel="stylesheet" href="styles.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /><link rel="start" href="index.html" title="Version Control with Subversion" /><link rel="up" href="svn.intro.html" title="Appendix A. Subversion Quick-Start Guide" /><link rel="prev" href="svn.intro.html" title="Appendix A. Subversion Quick-Start Guide" /><link rel="next" href="svn.intro.quickstart.html" title="High-speed Tutorial" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Installing Subversion</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="svn.intro.html">Prev</a> </td><th width="60%" align="center">Appendix A. Subversion Quick-Start Guide</th><td width="20%" align="right"> <a accesskey="n" href="svn.intro.quickstart.html">Next</a></td></tr></table><hr /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="svn.intro.install"></a>Installing Subversion</h2></div></div></div><p>Subversion is built on a portability layer called
      APR—the Apache Portable Runtime library.  The APR library
      provides all the interfaces that Subversion needs to function on
      different operating systems: disk access, network access, memory
      management, and so on.  While Subversion is able to use Apache
      as one of its network server programs, its dependence on APR
      <span class="emphasis"><em>does not</em></span> mean that Apache is a required
      component.  APR is a standalone library useable by any
      application.  It does mean, however, that like Apache,
      Subversion clients and servers run on any operating system that
      the Apache httpd server runs on: Windows, Linux, all flavors of
      BSD, Mac OS X, Netware, and others.</p><p>The easiest way to get Subversion is to download a binary
      package built for your operating system.  Subversion's website
      (<a class="ulink" href="http://subversion.tigris.org" target="_top">http://subversion.tigris.org</a>) often has these
      packages available for download, posted by volunteers.  The site
      usually contains graphical installer packages for users of
      Microsoft operating systems.  If you run a Unix-like operating
      system, you can use your system's native package distribution
      system (RPMs, DEBs, the ports tree, etc.) to get
      Subversion.</p><p>Alternately, you can build Subversion directly from source
      code, though it's not always an easy task. (If you're not
      experienced at building open source software packages, you're
      probably better off downloading a binary distribution instead!)
      From the Subversion website, download the latest source-code
      release.  After unpacking it, follow the instructions in
      the <code class="filename">INSTALL</code> file to build it.  Note that a
      released source package may not contain everything you need to
      build a command-line client capable of talking to a remote
      repository.  Starting with Subversion 1.4 and later, the
      libraries Subversion depends on (apr, apr-util, and neon) are
      distributed in a separate source package suffixed
      with <code class="filename">-deps</code>.  These libraries are now common
      enough that they may already be installed on your system.  If
      not, you'll need to unpack the dependency package into the same
      directory where you unpacked the main Subversion source.
      Regardless, it's possible that you may want to fetch other
      optional dependencies such as Berkeley DB and possibly Apache
      httpd.  If you want to do a complete build, make sure you have
      all of the packages documented in
      the <code class="filename">INSTALL</code> file.</p><p>If you're one of those folks that likes to use bleeding-edge
      software, you can also get the Subversion source code from the
      Subversion repository in which it lives.  Obviously, you'll need
      to already have a Subversion client on hand to do this.  But
      once you do, you can check out a working copy of the Subversion source
      repository from <a class="ulink" href="http://svn.collab.net/repos/svn/trunk/" target="_top">http://svn.collab.net/repos/svn/trunk/</a>:
      <sup>[<a id="id446328" href="#ftn.id446328" class="footnote">61</a>]</sup></p><pre class="screen">
$ svn checkout http://svn.collab.net/repos/svn/trunk subversion
A    subversion/HACKING
A    subversion/INSTALL
A    subversion/README
A    subversion/autogen.sh
A    subversion/build.conf
…
</pre><p>The above command will create a working copy of the latest
      (unreleased) Subversion source code into a subdirectory
      named <code class="filename">subversion</code> in your current working
      directory.  You can adjust that last argument as you see fit.
      Regardless of what you call the new working copy directory,
      though, after this operation completes, you will now have the
      Subversion source code.  Of course, you will still need to fetch
      a few helper libraries (apr, apr-util, etc.)—see
      the <code class="filename">INSTALL</code> file in the top level of the
      working copy for details.</p><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id446328" href="#id446328" class="para">61</a>] </sup>Note that the URL checked out in the example above
          ends not with <code class="literal">svn</code>, but with a
          subdirectory thereof called <code class="literal">trunk</code>.  See
          our discussion of Subversion's branching and tagging model
          for the reasoning behind this.</p></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="svn.intro.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="svn.intro.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="svn.intro.quickstart.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix A. Subversion Quick-Start Guide </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> High-speed Tutorial</td></tr></table></div></body></html>