Version Control with Subversion, 2nd Edition

Chapter 8. Embedding Subversion

Subversion has a modular design: it’s implemented as a collection of libraries written in C. Each library has a well-defined purpose and application programming interface (API), and that interface is available not only for Subversion itself to use but for any software that wishes to embed or otherwise programmatically control Subversion. Additionally, Subversion’s API is available not only to other C programs, but also to programs written in higher-level languages such as Python, Perl, Java, and Ruby.

This chapter is for those who wish to interact with Subversion through its public API or its various language bindings. If you wish to write robust wrapper scripts around Subversion functionality to simplify your own life, if you are trying to develop more complex integrations between Subversion and other pieces of software, or if you just have an interest in Subversion’s various library modules and what they offer, this chapter is for you. If, however, you don’t foresee yourself participating with Subversion at such a level, feel free to skip this chapter with the confidence that your experience as a Subversion user will not be affected.

Layered Library Design

Each of Subversion’s core libraries can be said to exist in one of three main layers—the Repository layer, the Repository Access (RA) layer, or the Client layer (see Figure 1 in the Preface). We will examine these layers shortly, but first, let’s briefly summarize Subversion’s various libraries. ...