
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
Inside the Working Copy Administration Area
|
177
Subversion’s language bindings unfortunately tend to lack the level of attention given
to the core Subversion modules. However, there have been significant efforts
towards creating functional bindings for Python, Perl, and Java. Once you have the
SWIG interface files properly configured, generation of the specific wrappers for all
the supported SWIG languages (which currently includes versions of C#, Guile,
Java, Mzscheme, OCaml, Perl, PHP, Python, Ruby, and Tcl) should theoretically be
trivial. Still, some extra programming is required to compensate for complex APIs
that SWIG needs some help generalizing. For more information on SWIG itself, see
the project’s website at http://www.swig.org/.
Inside the Working Copy Administration
Area
As we mentioned earlier, each directory of a Subversion working copy contains a
special subdirectory called .svn which houses administrative data about that work-
ing copy directory. Subversion uses the information in .svn to keep track of things
such as:
• Which repository location(s) are represented by the files and subdirectories in
the working copy directory
• What revision of each of those files and directories are currently present in the
working copy
• Any user-defined properties that might be attached ...