Edgewall Software

Version 14 (modified by Christian Boos, 16 years ago) ( diff )

Added reference to multiple SCM support in CVSTrac

Versioning System Backend

Currently, Trac is tightly integrated with 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 CVSTrac, a Project Management and Issue Tracking system which uses CVS as its Versioning System Backend (and like Trac, it uses SQLite as its DatabaseBackend, which isn't surprising considering the fact that the author of CVSTrac is also the author of SQLite) (1).

So, the current situation is pretty simple:

  • If you're using CVS, use CVSTrac
  • If you're using Subversion, use Trac
  • If you're using Darcs, use Trac+Darcs (see DarcsBackend the link is down)
  • If you're using Bazaar-NG, use Trac+Darcs since it also has support for Bazaar-NG.
  • 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.

So far, there has been interest in the following systems:

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


It should be mentioned that CVSTrac also aims to support more SCM backends, SVN and git being worked on.

Note: See TracWiki for help on using the wiki.