Welcome to the locutor Project!
Note: Hosting of locutor core library has moved to Google Code.
locutor is a full reimplementation of the Unix Subversion client developed by Normen Müller at Jacobs University focusing on smart management of change. Whereas Subversion compares text files line by line, locutor is able to use semantic knowledge about the document format to distinguish semantically relevant from irrelevant changes. Semantically irrelevant changes, for example, for LaTeX include whitespacing, comments, newlines, include/ import and URI normalization.
Furthermore, locutor identifies and maintains references within and between documents. Consequently, if locutor receives a change upon updating a file, it is not only able to determine its semantic relevance, but also to compute the effect of the change and determine the set of files that need to be rechecked.[Read more ...]
Major Features
- Repository access over http(s), svn, svn(+ssh) and file protocols.
- Working copy operations - all are supported.
- Redundancy Resolution
- locutor is reported to work on OSX, Linux, BSD and OpenVMS.
- locutor does not require native binaries, it works out of the box.
- Native Subversion configuration files are used by default.
- Latest locutor supports Subversion 1.5.2.
locutor vs. Subversion
| Feature | Subversion | locutor |
|---|---|---|
| Client/ Server architecture | YES | NO (only client) |
| Scoping | NO | YES |
| Redundancy Resolution | NO | YES |
| Computation/ management of dependency graphs within/ between versioned entries across working copy boarders. | NO | YES |
| Versioning of dependency graphs. | NO | YES |
| Semantic difference computation based on a sophisticated equality theory. | NO | YES |
| Fragmentation/ classification of computed difference. | NO | YES |
| Change/ conflict propagation. | NO | YES |
| Active users | ˜ 1,000,000 | ˜ 20 (HELP!) |
| Ownership | Tigris | Normen Müller |
