Subversion (SVN)

Release date: 
Monday, 27 December, 2004




Authors/Port authors:

Subversion - also known as SVN - for OS/2, based on latest GNU C library.

For jEdit editor, a Java based Subversion (ver. 1.7) plugin is available; it doesn't require svn installed on the local system.

This software is distributed in two modes:
  • as compressed package that you have to download and manually install; if prerequisites are required, you will have to manually install them too;
  • as RPM package; you can install it using your favorite rpm package manager, that will take care to download and install both the software and its prerequisites.
Choose the installation mode that you prefer. Please note that not all the versions are available in both the installation modes.

Installation with rpm

This program is installable using the rpm package manager. See below for the install string. Required prerequisites are automatically processed by the package manager and, if needed, downloaded and installed.

subversion- (05/10/2011)
Repository: Netlabs stable

Manual installation

Program is distributed as ZIP package: download to temporary directory and unpack to destination folder. See below for download link(s).

Following ones are the download links for manual installation:

Subversion (SVN) v. 1.7.21 (10/8/2015, Paul Smedley (Smedles)) Readme/What's new
Subversion 1.7.21 for OS/2 & eComStation The goal of the Subversion project is to build a version control system that is a compelling replacement for CVS in the open source community. The software is released under an Apache/BSD-style open source license. Requires libc066.dll - which is available from This has had minimal testing, but I have used it successfully to check out code from several subversion repositories. Changes in 1.7.21 - 2015-08-10 release - Updated to v1.7.21 All feedback is appreciated to, bugs should be entered in the bugtracker at If you like this software and want to support continued ports, please consider donating via PayPal via the link at, or via the Mensys online store at Cheers, Paul Smedley Adelaide, Australia 10th August, 2015  local copy
Subversion (SVN) v. 1.1.2 (27/12/2004, Brian Havard) Readme/What's new
Subversion, a version control system. ===================================== $LastChangedDate: 2004-12-19 03:45:15 +1000 (Sun, 19 Dec 2004) $ Contents: I. A FEW POINTERS II. DOCUMENTATION III. PARTICIPATING IN THE SUBVERSION COMMUNITY IV. QUICKSTART GUIDE V. CONVERTING FROM CVS I. A FEW POINTERS For an overview of the Subversion project, visit Once you have a Subversion client you can get the latest version of the code with the command: $ svn co subversion II. DOCUMENTATION The main documentation is the Subversion Book, written in DocBook XML, which lives in the doc/ tree. If you wish to build the documentation from source, read doc/book/README. Otherwise, an on-line version of the book can be found at See COPYING for copyright information. See HACKING for development information. See INSTALL for installation information. III. PARTICIPATING IN THE SUBVERSION COMMUNITY First, read the HACKING file! It describes Subversion coding and log message standards, as well as how to join discussion lists. Talk on IRC with developers:, channel #svn. Read the FAQ: IV. QUICKSTART GUIDE Please note that this section is just a quick example for people who want to see Subversion run immediately. It's not an excuse to ignore the book! The Subversion client has an abstract interface for accessing a repository. Three "Repository Access" (RA) implementations currently exist as libraries: libsvn_ra_dav: accesses a networked repository using WebDAV. libsvn_ra_local: accesses a local repository using Berkeley DB. libsvn_ra_svn: accesses a remote repository using a custom protocol. You can see which methods are available to your 'svn' client by running 'svn --version'. The following example assumes that ra_local is available to your client. (If you don't see ra_local, it probably means that Berkeley DB wasn't found when compiling your client binary.) 1. svnadmin create /path/to/repos - this creates a new directory, 'repos'. Make sure that /path/to/repos/ is on local disk, NOT a network share. - make SURE you have complete recursive read/write access to the newly created 'repos' directory. - understand that the repository is mainly a collection of BerkeleyDB files; you won't actually see your versioned data if you peek in there. 2. svn import /tmp/project file:///path/to/repos -m "Initial import" - /tmp/project is a tree of data you've pre-arranged. If you can, use this layout, as it will help you later on: /tmp/project/branches/ /tmp/project/tags/ /tmp/project/trunk/ foo.c bar.c baz.c etc. 3. svn checkout file:///path/to/repos/trunk project - this creates a 'project' directory which is a working copy of the /trunk directory in the repository. 4. Try using the repository: - edit a file in your working copy. - run 'svn diff' to see the changes. - run 'svn commit' to commit the changes. - run 'svn up' to bring your working copy up-to-date. Be sure to read chapters 2 and 3, they're a critical introduction to the svn commandline client. 5. Get a real server process running (either apache or svnserve) so that your repository can be made available over a network. Read chapters 5 and 6 to learn about how to administer a repository and how to set up a server process. *** NEWBIES BEWARE: The absolute most common stumbling block for newbies is problems with permissions and ownership on the repository. Any process that opens the repository must have complete read/write access to it. This goes for any tool ('svnadmin', 'svnlook') or any server process (apache, svnserve), or your own svn client, if it's accessing via file:///. Look at the last section in chapter 6 to understand how to tweak repository ownership and permissions for multiple users and processes. V. CONVERTING FROM CVS If you're a CVS user trying to move your CVS history over to Subversion, then be sure to visit the 'cvs2svn' project: You can get the latest released version of the cvs2svn converter from the project downloads area: Please note that the cvs2svn project is a *separate* project from Subversion. If you have problems with cvs2svn or are confused, please email the cvs2svn project's mailing lists, not the Subversion lists. Finally, be sure to see Appendix A in the Subversion book. It contains a very quick overview of the major differences between CVS and Subversion.  local copy
Record updated last time on: 16/10/2022 - 21:31

Translate to...

Add new comment