We meet Veracity - a new distributed version control system

Main differences from Git

1. Availability of local revision numbers. Veracity, like Git, uses cryptographic hash functions for version control of individual files. However, in the local repository, each commit receives a unique revision number, as it happens in Subversion. The revision number and hash can be used interchangeably and are often indicated by a colon.
2. Support multiple hash functions. Everyone knows that Git uses the SHA-1 function in its work. Veracity allows you to choose between SHA-1 , SHA-2 or Skein .
3. Formal file renaming. Git, when renaming files, actually deletes the file, and then creates a file with the same content and new name. Veracity does exactly rename the existing file.
4. Support file locks. Centralized version control systems like Subversion support 2 work schemes: file locking (svn lock \ svn unlock) and merging changes (svn merge). Although Git and other distributed version control systems often use a central repository in their work, they lack a file locking mechanism. Veracity corrects this flaw. It is clear that to block files, you need access to remote repositories through the network.
5. Stamp support. Veracity includes a completely new functionality, called stamps. A stamp is a stamp from arbitrary text that a developer can attach to any commit. Unlike tags, which associate a unique name for each commit, the same stamp can mark an arbitrary number of commits. For example, when using a continuous integration system, you can put a “Tests passed” stamp on commits that have passed a series of tests without errors, just like the manufacturers of equipment put a “qc pass” stamp (quality controll passed) on each sample produced.
6. Decentralized repository database. Many version control systems store repository data within the working directory. For example, Git has a .git folder in which binary objects, trees, commit objects, an index, a configuration, hooks, etc. are stored. Veracity stores most of the service information on the repository outside the working directory in a special database. This, for example, allows you to have several working directories for one repository at once.
7. Built-in Javascript interpreter. Veracity uses Javascript as the main scripting language. For example, you can write hooks in the form of Javascript functions. There is also a built-in Javascript API that can be used to write server-side web applications using Veracity. It is logical that JSON is used to store the serialized data.
8. Embedded web application for repository review. With one command, you can start the embedded web server with an application that allows you to view the contents of the repository, the change history, the project build status, or the bug tracker.

Installation

1. Build from source codes. The system is written in C, like some other version control systems (for example, Git, Subversion or Fossil), so we will have to deal with installing source dependencies and utilities like cmake and make. For those who like these things, here are build instructions for Linux and for Windows .
2. Install from binary package. To start picking Veracity faster, it will be much easier to use binary packages that can be downloaded on the download page . There are binary packages for Debian-compatible systems (* .deb: x86, x64) and for Windows (* .msi: x86, x64).

Basic commands

$vv add filename1 filename2 ~/thisdir 

 $vv addremove dirname1 

 $vv branch $vv branch add devel 

 $vv cat filename 

 $vv checkout 

 $vv clone http://example.com/repos/reponame reponame 

 $vv comment --rev=123 --message='A new comment' 

 $vv commit --message='Commit message' 

 $vv config set whoami/username vania-pooh 

 $vv diff --rev=3 filename 

 $vv diffmerge --rev=3 filename 

 $vv export reponame ~/copyhere 

 $vv fast-export reponame ~/backupname.fi 

 $vv fast-import --hash=SHA2/512 ~/backupname.fi 

 $vv heads 

 $vv help branch new 

 $vv history 

 $vv incoming 

 $vv init reponame dirname 

 $vv leaves 

 $vv lock filename 

 $vv locks 

 $vv merge -r 37939b07309af8232c44048ca0a1633c982b7506 

 $vv move filename ~/newdir 

 $vv outgoing 

 $vv parents 

 $vv pull # ,          vv update 

 $vv push # ,           

 $vv remove ~/repo/filename 

 $vv rename ~/repo/oldfile ~/repo/newfile 

 $vv repo info 

 $vv resolve ~/filename #         

 $vv revert ~/filename1 ~/filename2 

 $vv serve --port=8080 --public 

 $vv stamp add approved --rev=3 

 $vv status 

 $vv tag add tagname --rev=3 

 $vv unlock filename 

 $vv update 

 $vv user create vania-pooh 

 $vv version 

 $vv whoami anotherUser 

 $vv zip ~/backup/archive.zip 

File location

Veracity embedded application

 $vv serve --port=8080 --public # --public     . 

Hosting projects Veracity

Links

• Official site
• Hosting Veracity repositories
• The book on Veracity , at the moment the only more or less detailed description of the main commands and work cycle.

Conclusion