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 does not 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.
The easiest way to get Subversion is to download a binary package built for your operating system. Subversion's website (http://subversion.tigris.org) 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.
Alternately, you can build Subversion directly from source
code. From the Subversion website, download the latest
source-code release. After unpacking it, follow the
instructions in the
INSTALL file to build
it. Note that a released source package contains everything you
need to build a command-line client capable of talking to a
remote repository (in particular, the apr, apr-util, and neon
libraries). But optional portions of Subversion have many other
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
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 checkout a working copy of the Subversion source repository from http://svn.collab.net/repos/svn/trunk/: 
$ 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 …
The above command will checkout the bleeding-edge, latest
version of the Subversion source code into a subdirectory
subversion in your current working
directory. Obviously, 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,
INSTALL file in the
top level of the working copy for details.
 Note that the URL checked out in the example above
ends not with
svn, but with a
subdirectory thereof called
our discussion of Subversion's branching and tagging model
for the reasoning behind this.