= Version Control System Currently, Trac is tightly integrated with [http://subversion.apache.org Subversion] and [http://git-scm.org Git]. Starting with Trac 0.12, a given TracEnvironment can handle multiple repositories of the same or different versioning systems (see TracRepositoryAdmin). Also, nothing prevents you from setting up multiple Trac Environments on top of the same repository. This can be handy to manage separately different products which share the same code repository. == Other Versioning Systems 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. Like Trac, it uses [http://www.sqlite.org SQLite] as its DatabaseBackend, which isn't surprising considering the fact that the author of CVSTrac is also the author of SQLite ^[wiki:VersioningSystemBackend#a1 (1)]^. The versioning systems which are supported by '''Trac''' out of the box: * [http://subversion.apache.org Subversion], provided the Python bindings for Subversion are installed. See TracSubversion for more details. * [http://git-scm.com/ Git], provided the `git` command line tools are installed. As an optional component for Trac, it needs to be //enabled// in the configuration. See TracGit for more details. The other versioning systems known to work with Trac are: * [https://www.mercurial-scm.org/ Mercurial], as a plugin for Trac, see TracMercurial. * [http://www.darcs.net/ Darcs], with '''Trac+Darcs''', see TracDarcs, [http://progetti.arstecnica.it/trac+darcs/wiki/DarcsBackend DarcsBackend], and also #638. * [http://bazaar.canonical.com/en/ Bazaar], also with '''Trac+Darcs'''. since it also has support for Bazaar. Contrary to Darcs support, this only works for 0.9, since the original author of Bazaar support, Johan Rydberg, is not working on this any more. An attempt to support >=0.10 versions is available at https://launchpad.net/trac-bzr. * [http://www.perforce.com/ Perforce], as a plugin for Trac, see [trachacks:PerforcePlugin PerforcePlugin] and #257. * [http://monotone.ca/ Monotone], as a plugin for Trac, see [http://tracmtn.1erlei.de/ TracMTN] (beta) and #1492. * [http://www.march-hare.com/cvspro/ CVSNT], as a plugin for Trac, see [trachacks:TracCvsntIntegrationPlugin TracCvsntIntegrationPlugin], status is pre-alpha. * [http://www.visualsvn.com VisualSVN] integrates Subversion for Windows users, see TracOnWindows. In addition, there has been interest in the following systems: * #978: ~~[http://svk.elixus.org SVK] support~~ (SVK is no longer maintained) * #893: ~~[http://regexps.srparish.net/www/ Arch] support~~ (Arch is no longer maintained) * #2037: [http://www-306.ibm.com/software/awdtools/clearcase ClearCase] support * #2643: [http://www.nongnu.org/cvs/ CVS] support * Another [http://dev.laptop.org/git/projects/trac-git Git plugin] developed for/by [http://one.laptop.org/ One Laptop Per Child] * TBD: [https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools#darcs-git darcs-git] support for darcs-git backend might also be useful. ---- ===== 1) ===== CVSTrac also aims to support more [http://www.cvstrac.org/cvstrac/wiki?p=ScmTrac SCM backends], SVN and git being worked on.