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) ⁽¹⁾.

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)
• If you're using ​Bazaar-NG, use Trac+Darcs since it also has support for Bazaar-NG (see ​BzrngBackend)
• If you're using ​Mercurial, use TracMercurial
• If you're using ​Perforce, use ​PerforcePlugin (see also ticket #257)
• 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 0.10.

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

• #978: ​SVK support (as mentioned in that ticket, SVK is actually already supported in some way)
• #893: ​Arch support
• #638: ​darcs support
• #1492: ​monotone support
• TBD: ​bzr support (This one is interesting in that it is written in Python.)
• TBD: ​darcs-git support for darcs-git backend might also be useful.
• #2037 ClearCase support

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

---

1)

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