Edgewall Software

Changes between Version 109 and Version 110 of TracSubversion


Ignore:
Timestamp:
Jul 17, 2012, 10:43:26 PM (12 years ago)
Author:
Christian Boos
Comment:

add note for 1.0 and the #tracopt move done in r11082.

Legend:

Unmodified
Added
Removed
Modified
  • TracSubversion

    v109 v110  
    44
    55Trac has supported the [http://subversion.apache.org Subversion] VersionControlSystem since day one. Actually, Trac was even named `svntrac` back then!
     6
     7However, things change and other version control systems gain in popularity... in Trac 1.0 we also support Git as an optional component below `tracopt.versioncontrol.git.*`. As to not make any first class, second class distinction, we also decided to move the subversion support over there, in `tracopt.versioncontrol.svn.*`.
     8
     9{{{#!box info
     10[=#tracopt]
     11In Trac 1.0 (trunk, starting from r11082), the components for Subversion support have been moved below `tracopt.` so you need to explicitly enable them in your TracIni#components-section:
     12{{{
     13[components]
     14tracopt.versioncontrol.svn.* = enabled
     15}}}
     16}}}
    617
    718This page is intended to collect all the specific tips and tricks
     
    212223that the Python bindings for Subversion can't be loaded by Trac.
    213224
     225For Trac 1.0 (trunk), another common cause might simply be that the components for Subversion, are not enabled, since they're now optional. See [#tracopt] above for more details.
     226
    214227If you use Debian an try this: TracOnDebianSarge
    215228