|Version 22 (modified by 14 years ago) ( diff ),|
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).
The versioning systems known to work with Trac are:
- Subversion, which is supported by Trac out of the box, provided you have Subversion and its Python bindings installed (preferred version is still 1.2.3)
- Darcs, with Trac+Darcs (see DarcsBackend, and also #638)
- Bazaar-NG, also with Trac+Darcs since it also has support for Bazaar-NG (see BzrngBackend)
- Mercurial, as a plugin for Trac (see TracMercurial)
- Perforce, as a plugin for Trac (see PerforcePlugin (see also ticket #257)
- If you're using something else, you're on your own…
…but it should be much easier now to add support for another backend,
as of Trac 0.10 (but this is already available in the
Among other things, Subversion is not a strict requirement anymore,
and there's support for pluggable backends (
see TracMercurial for an example).
In addition, 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
- #1492: monotone support
- #2037: ClearCase support
- #2643: CVS support
- TBD: Git support
- TBD: darcs-git support for darcs-git backend might also be useful.
It should be mentioned that CVSTrac also aims to support more SCM backends, SVN and git being worked on.