Free control system software for linux

tclDBRCS is a database-oriented revision control system which features full project/tag/branch support. The application supports encryption of file content, CVS import, infinite branching of branches, entire diff or merge of project, RC of binary files, empty directory storage, removal without losing history, and more. No specialized server is needed outside of PostgreSQL, and all operations are executed on the client machine.
Install required packages:
1.1) Install PostgreSQL
1.2) Install GNU diffutils
1.3) Install XDELTA3
1.4) Install CVS (TortoiseCVS for example)
Install tcldbrcs:
2.1) untar the package tcldbrcs- .tar.gz
2.2) Edit bin/dbrcs.bat, bin/initdb.bat bin/tkdbrcs.bat to match your installation path
2.3) Edit etc/configuration_options.src.tcl, etc/access_keys.src.tcl
Start a shell and add /bin in your path
Enhancements:
- This release adds support for SQLite.
- There are some bugfixes.

The Bazaar VCS is a simple decentralized revision control system. Decentralized revision control systems give users the ability to branch remote repositories to a local context.
Users can commit to local branches without requiring special permission from the branches that they branched from.
Whats New in 0.18 Stable Release:
- This release provides over 50 changes, including 15 bugfixes, 16 user-visible improvements, and over 20 enhancements to internals such as test suite enhancements, cleaner APIs, and much more developer documentation.
- Some of the highlights include better criss-cross merging, improved usability, and faster bundle, merge, missing, pull, update, and info operations.
Whats New in 0.90.0 RC1 Development Release:
- Some of the highlights include pyrex implementations of some performance critical functions, algorithm changes giving performance improvements to merging and merge directive generation, a send command that will make contributing changes back easier, and connection sharing to reduce the number of connections that must be made to a remote location in some situations.
- This release includes 10 bugfixes, 25 user visible improvements, and over 20 enhancements to the internals.

Apache::SiteControl is a Perl web site authentication/authorization system.

SYNOPSIS

See samples/site for complete example. Note, this module is intended for mod_perl. See Apache2::SiteControl for mod_perl2.

Apache::SiteControl is a set of perl object-oriented classes that implement a fine-grained security control system for a web-based application. The intent is to provide a clear, easy-to-integrate system that does not require the policies to be written into your application components. It attempts to separate the concerns of how to show and manipulate data from the concerns of who is allowed to view and manipulate data and why.

For example, say your web application is written in HTML::Mason. Your individual "screens" are composed of Mason modules, and you would like to keep those as clean as possible, but decisions have to be made about what to allow as the component is processed. SiteControl attempts to make that as easy as possible.

DEVELOPERS VIEWPOINT - EXAMPLE

In this document we use HTML::Mason to create examples of how to use the control mechanisms, but any mod_perl based system should be supportable.

A good mason component tries to do most of the perl processing in a separate block, so that simple substitutions can be made in HTML in the rest of the page. This makes it much easier for web developers and perl developers to co-exist on a project.

The SiteControl system tries to make it possible to continue to follow this model. You obtain a user object and permission manager from the SiteControl system. These are intended to be opaque data types to the page designer, and are defined elsewhere (see USERS). The actual web page component should carry these objects around without implementing anything in the way of policy.

Project Dune provides an issue tracker integrated with source code control systems.
Project Dune is a Web-based issue tracker that is fully integrated with source code control systems, which enables code inspections in the browser.
The project aims to automate the full cycle of development, from estimation to release.
This allows more time for productive tasks like architecture, design and coding. Especially if you have a quality plan in place based on ISO or CMM, you will find this software useful.
It is built for Tomcat with GWT, Hibernate, Java, Dozer, using the Postgres database.
Enhancements:
- An entire new layout.
- An administration module has been added.
- The inspection m- Eodule has been separated, and binary inspections added.
- Many fixes and features have been implemented.

Bazaar-GTK is a GTK+ frontend for the Bazaar version control system.
The project provides Nautilus integration and a stand-alone application for browsing Bazaar branches.
Provided Commands
- gcommit
- gdiff
- visualise
- gannotate
- gbranch
Provided classes
- GAnnotateWindow
- GCommitDialog
- CloneDialog
- DiffWindow
- BranchWindow (Visualisation)

DACS is an open source identity management and access control system for web services. The web services can be virtually any static or computational resources provided through HTTP.
Main features:
- a flexible and powerful role-based access control system;
- a set of feature-rich authentication methods;
- an Apache 2.0.X module and suite of CGI programs;
- a federated identity management system (single sign-on);
- oriented towards (but not limited to) controlling access to web service requests made using standard web browsers;
- a collection of web services that can provide access control and identity management functionality to your middleware;
- a C/C++ toolkit for building new authentication and access control functionality into programs, whether web-based or not;
- for Unix-type platforms (currently), such as Linux, FreeBSD, and Solaris; and has
- an open, lightweight design and portable implementation.
DACS can help you to manage access to web resources in many situations, whether you have just one web server, several web servers at one site, or many web servers spread across the Internet.
You may find it to be useful simply as a universal authentication mechanism for a single Apache server or as a full-fledged, single sign-on multi-server identity management and access control system.
DACS may be of interest to developers more interested in authentication functionality than access control. DACS identities can be integrated with HTTP-based clients, whether interactive or not, and non-web based client/server applications.
Designed and implemented by DSS, development of DACS was initiated in May, 2001. DACS is a key component of Canadas National Forest Information System (NFIS).
Enhancements:
- This is primarily a bug fix and minor enhancements release. DACS is security software - we urge all users to upgrade to the latest release.