= Versioning System Backend =

Currently, Trac is tightly integrated with 
[http://subversion.tigris.org Subversion].

Any given TracEnvironment addresses one and only one 
Subversion Repository. However, nothing prevents you 
to setup multiple Trac Environments on top of the same
Subversion Repository. This can be handy to manage 
separately different products which share the same code 
repository.



== Other Versioning System ==

As mentioned in the TracHistory, Trac was inspired
by [http://www.cvstrac.org CVSTrac], a Project Management
and Issue Tracking system which uses CVS as its Versioning 
System Backend (and quite interestingly, it also uses 
[http://www.sqlite.org SQLite] as its DatabaseBackend).

So, the current situation is pretty simple:
 * If you're using [https://www.cvshome.org/ CVS], use '''CVSTrac'''
 * If you're using [http://subversion.tigris.org Subversion], use '''Trac'''
 * If you're using something else, you're on your own...

But as Trac is evolving, it will support more
versioning system backends.  This is a stated
goal for the [milestone:2.0 Milestone 2.0].

So far, there has been interest in the following systems:
 * #978: [http://svk.elixus.org SVK] support (as mentioned in that ticket, SVK 
   ''is'' actually already supported in some way)
 * #893: [http://regexps.srparish.net/www/ Arch] support
 * #257: [http://www.perforce.com/ Perforce] support
 * #638: [http://abridgegame.org/darcs/ darcs] support
 * #1492: [http://venge.net/monotone/ monotone] support
 * TBD: [http://bazaar-ng.org/ bzr] support  (This one is interesting in that it is written in Python.)

There's even a request that Trac should be usable ''without''
any underlying versioning system (#156).