David Abrahams wrote:
... Trac needs a separate database, so clearly it doesn't depend exclusively on SVN for storage. In all the trac documentation I can find, the only thing it says about subversion is that Trac will let you browse the SVN repository. Surely it doesn't make sense to make SVN a *requirement* if all Trac is doing with SVN is to provide a browser?
SVN is not a requirement anymore since version 0.10.
Can someone point me to more complete information about what Trac is doing with SVN and what sort of integration I get beyond repository browsing? Also (in case it isn't obvious), I'm requesting that the docs be updated to reflect this information (or more clearly highlight it, if I've missed something).
In the TracGuide, there's the TracBrowser, TracChangeset and TracRevisionLog pages which explain what you can do. Also, the integration is achieved by the way of the TracLinks in the wiki syntax, which enables you to "talk" about your changesets
or source files from any part of the system (tickets, wiki pages, etc.) Lastly, there's a contributed post-commit-hook script for Subversion, which will comment on and otherwise manipulate your tickets in Trac depending on what has been written in the changeset message. -- Christian _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
