Free revision control system software for linux

The Bazaar Revision Control System is a changeset-oriented revision control system based on Arch that makes it possible to retain previous changes to projects and coordinate development with other developers.
Its goal is to speed development of an upwards- compatible version of Arch.
Main features:
- All the transparent and robust storage features of GNU Arch.
- seamless upgrade path to [WWW] bazaar-ng
- direct support for URLs - one command can checkout or merge from remote locations.
- integrated GPG support - zero setup for most signed archive situations
- faster - checkout, most local operations, commits
- svn-like diff, switch, import, export, log commands
- Explicit tracking of conflicts, preventing accidental commits of files with conflicts
- single merge command that allows merging between arbitrary branches.
- Daily builds of the latest code (Downloads).
- fully compatible with tla - drop in and start using
- supports debian version numbers in branch names
- annotate support
- internationalised via gettext and [WWW] Rosetta.
- Python bindings.
Enhancements:
- More Solaris fixes.
- SSL support and ~/.authinfo support.
- Many UI tweaks.
- A number of bugfixes.

A Simple Version Control System is an easy to install and easy to to use version/revision control system.
ASVCS differs from most other version control systems in that ASVCS is designed to keep track of files in place. ASVCS does not allow any changes to be made to files, all changes require the users to change files externally with FTP or SSH access.
ASVCS is very easy to setup and use. Users do not need to work with repository, branches, commit and check-out files. All a user needs to do is upload the changes files and click Update or if enabled just wait for it to be updated automatically.
ASVCS is ideal for small projects or personal use, though it can also be used by large project how do not need or want the complexity of most version control systems.
Main features:
- asy to install and use
- Written in PHP
- Can track binary or text files
- Automatic file tracking (requires cron support)
- Diffs of revisions
- Easy user access management
- Entirely Web based
- Skinable
- Open source (MIT/expat license)

AstroCam is a C based Stepmotor Control system including a PHP-Webinterface.
The first AstroCam version was released in Dec 2001 and was written in C+Tcl/Tk. After i saw, that the combination of Tcl/Tk and C code wasnt a good thing, I wrote a CGI webinterface and a Gtk GUI. A few years later, I removed both parts, rewrote AstroCam completely, built an PHP webinterface and changed the communication system between its components to message queues.
Main features:
Supported Operating Systems:
- OpenBSD i386
- NetBSD i386
- FreeBSD i386
- Linux 2.2/2.4/2.6 i386
Supported Browsers:
- All browsers with IFrame-support (e.g. Konqueror, Internet Explorer, Mozilla/Firefox) should work. Netscape 4.x doesnt work.
Enhancements:
- The installer now can handle directories of the MyServer webserver too.

active acoustic vibration control tool is a set of basic tools for monitoring and modulating audio noise.

The tools aim toward a set of codes and algorithms for monitoring noise signal and modulation and reducing them using active noise control priciples.

Active noise control and soundproofing is a relativly recent development (first researched around 30 years ago), and has been in constant development for many and varied situations and applications.

The basic concept of active noise control is the aplication of equal and opposite force to cancel out vibration.

The project attempts to provide a starting point and library for experimentation into various methods of digital signal processing for active noise reduction and soundproofing.

Noise cancellation has been used in many environments currently active control is best used in constant vibrations with lower frequencys.

The principle is of controlling the noise level by adding an equal and opposite sound to the noise in the environment. The basic principle may be simple but the actual effectivness depends on many environmental factors.

Generally simplistic out of phase sound wave is used which works to some extent and requires little processing (a simple XOR with -1) this will tend to leave a large number of artifacts as the amplitude of higher frequency components (above i->o delay time) rises.

i->o processing delay
e transducer efficiency
p sound propagation characteristics
r reflections

The project aims to provide a framework for many dsp architectures, dac/adc chips, transducers and monitors.

Create tools for acoustic calibration and data logging hardware
To simplify implementation of active noise and vibration control systems.
To provide an open source standard for use within the industry and education.
To encourage hardware producers to distribute standard interface descriptions for their hardware
Enable low cost development of systems using COTS consumer hardware for noise and vibration control.

Distributed Concurrent Versioning System (DCVS) project extends the well-known version control system CVS and the file distribution and synchronization program CVSup with functionality to distribute CVS repositories with local lines of development and handle synchronization of the distributed repositories automatically in the background.
Development lines (branches) are owned by a repository server, repository servers efficiently update each other via CVSup, and CVS ensures correct server use on checkin and branch creation.
Enhancements:
- This release adds miscellaneous bugfixes and the security patches of CVS 1.12.13.
- There are now installation packages for Windows to be installed on Cygwin, for SUSE Linux 10, for FreeBSD 4, 5, and 6, and for Fedora Core 4.

Sin project is a framework that implements Continuous Integration on top of the Subversion version control system.
This can help to improve the overall productivity of your development team by reducing the number of build breakage experiences or even eliminating them entirely.
Main features:
Stable codebase
- Sin ensures that your codebase is stable at all times. Here, stable is defined as the codebase obeying all rules you set up in your Sin system (codebase must build, all tests must pass, etc.).
Sin saves your time
- Developers will never be bothered with the consequences of incorrect changes that cause broken builds. Sin automatically reverts (undoes) any change that violates one or more rules and notifies the developer who checked in the change, of the problem.
Sin is easy to set up and use
- Use the graphical setup application to set up your Sin system in minutes. Once set up, developers hardly know Sin is there until they check in a change that breaks the build - in which case Sin might just have saved the developer from public humiliation.
Easy reviewing
- Sin can send checked in changes in color-coded html by email for easy reviewing by other developers.
Use your existing build system
- No change to your existing build system is needed as long as your system can be built from the command line.
Sin is scalable
- Sin is a distributed system based on open standards like SOAP webservices and is easy to expand to handle new loads.

File::Revision is a Perl module to return a name of non-existing backup file with a revision id.

SYNOPSIS

#######
# Subroutine interface
#
use File::Revision qw(new_revision num2revision parse_options revision2num revision_file rotate);

($file_name, $next_revsion) = new_revision($file, @options);
($file_name, $next_revsion) = new_revision($file, @options);
($file_name, $next_revsion) = new_revision($file, %options);

$revision_letter = num2revision($revision_number);

$options = parse_options($file, @options);
$options = parse_options($file, @options);
$options = parse_options($file, %options);

$revision_number = revision2num($revision_letter;

$file_name = revision_file($revision_number, $options);

$file_name = rotate($file, @options);
$file_name = rotate($file, @options);
$file_name = rotate($file, %options);

#######
# Object interface
#
$self = File::Revision; # or
$self = new $class; # where $class::@ISA contains File::Revision

($file_name, $next_revsion) = $self->new_revision($file, @options);
($file_name, $next_revsion) = $self->new_revision($file, @options);
($file_name, $next_revsion) = $self->new_revision($file, %options);

$revision_letter = $self->num2revision($revision_number);

$options = $self->parse_options($file, @options);
$options = $self->parse_options($file, @options);
$options = $self->parse_options($file, %options);

$revision_number = $self->revision2num($revision_letter;

$file_name = $self->revision_file($revision_number, $options);

$file_name = $self->rotate($file, @options);
$file_name = $self->rotate($file, @options);
$file_name = $self->rotate($file, %options);

The File::Revision program modules provides the name of a non-existing file with a revision identifier based on the a file name $file. This has many uses backup file uses. There are no restrictions on the number of backup files or the time to live of the backup files.

A typical use would be to create a backup file for If the revised file passes does not pass all validity checks, use the backup file to replace or repair the revised file. This minimizes loses import data when revising files.

Better yet, create a temporary file, using one of the temp file name program modules. Revise the temp file. Once it passes all valitity checks, rename the original file to the backup file and rename the temp file to the original file. This allows full use of the original file until a validated revison is ready to replace it.

The File::Revision program module also supports limiting the backup files and delete the oldest once File::Revision reaches the rotation limit.

SDMS is an open-source system that allows you to store any document in a database via a bunch of webpages.

That was the short description, now comes the long one. SDMS uses PHP to provide you with a pretty interface to a MySQL server that allows you to store and retrieve documents and to share those documents between users.

In addition, the system uses ACL (Access Control Lists) to grant access rights to documents on a per-user basis.

So what is all this good for? Well, it for instance allows you to distribute project documentation on a need-to-know basis, whilst keeping a central repository of documents that is accessible to all team members and easy to manage.