Edgewall Software

Changes between Initial Version and Version 1 of VersionControlSystem


Ignore:
Timestamp:
Nov 24, 2004, 3:07:35 PM (17 years ago)
Author:
cboos@…
Comment:

Discussion Trac's underlying versioning system(s)

Legend:

Unmodified
Added
Removed
Modified
  • VersionControlSystem

    v1 v1  
     1= Versioning System Backend =
     2
     3Currently, Trac is tightly integrated with
     4[http://subversion.tigris.org Subversion].
     5
     6Any given TracEnvironment addresses one and only one
     7Subversion Repository. However, nothing prevents you
     8to setup multiple Trac Environments on top of the same
     9Subversion Repository. This can be handy to manage
     10separately different products which share the same code
     11repository.
     12
     13
     14
     15== Other Versioning System ==
     16
     17As mentioned in the TracHistory, Trac was inspired
     18by [http://www.cvstrac.org CVSTrac], a Project Management
     19and Issue Tracking system which uses CVS as its Versioning
     20System Backend (and quite interestingly, it also uses
     21[http://www.sqlite.org SQLite] as its DatabaseBackend).
     22
     23So, 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
     28But as Trac is evolving, it will support more
     29versioning system backends.  This is a stated
     30goal for the [milestone:2.0 Milestone 2.0].
     31
     32So 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
     38There's even a request that Trac should be usable ''without''
     39any underlying versioning system (#156).
     40
     41
     42
     43
     44