| | 1 | = Versioning System Backend = |
| | 2 | |
| | 3 | Currently, Trac is tightly integrated with |
| | 4 | [http://subversion.tigris.org Subversion]. |
| | 5 | |
| | 6 | Any given TracEnvironment addresses one and only one |
| | 7 | Subversion Repository. However, nothing prevents you |
| | 8 | to setup multiple Trac Environments on top of the same |
| | 9 | Subversion Repository. This can be handy to manage |
| | 10 | separately different products which share the same code |
| | 11 | repository. |
| | 12 | |
| | 13 | |
| | 14 | |
| | 15 | == Other Versioning System == |
| | 16 | |
| | 17 | As mentioned in the TracHistory, Trac was inspired |
| | 18 | by [http://www.cvstrac.org CVSTrac], a Project Management |
| | 19 | and Issue Tracking system which uses CVS as its Versioning |
| | 20 | System Backend (and quite interestingly, it also uses |
| | 21 | [http://www.sqlite.org SQLite] as its DatabaseBackend). |
| | 22 | |
| | 23 | So, the current situation is pretty simple: |
| | 24 | * If you're using CVS, use '''CVSTrac''' |
| | 25 | * If you're using Subversion, use '''Trac''' |
| | 26 | * If you're using something else, you're on your own... |
| | 27 | |
| | 28 | But as Trac is evolving, it will support more |
| | 29 | versioning system backends. This is a stated |
| | 30 | goal for the [milestone:2.0 Milestone 2.0]. |
| | 31 | |
| | 32 | So far, there has been interest in the following systems: |
| | 33 | * #978: SVK support (as mentioned in this ticket, SVK |
| | 34 | ''is'' actually already supported in some way) |
| | 35 | * #893: Arch support |
| | 36 | * #257: Perforce support |
| | 37 | |
| | 38 | There's even a request that Trac should be usable ''without'' |
| | 39 | any underlying versioning system (#156). |
| | 40 | |
| | 41 | |
| | 42 | |
| | 43 | |
| | 44 | |
