Free cvs repository software for linux

Cache::Repository is a Perl module used to cache generic file repository.

SYNOPSIS

my $rep = Cache::Repository->new(
style => Filesys,
# options for the F::R driver
);
$rep->add_files(tag => groupname,
files => @filenames,
basedir => /tmp,
move => 1,
);
$rep->add_filehandle(tag => anothergroup,
filename => blah,
filehandle => $fh,
mode => 0755);
$rep->set_meta(tag => groupname,
meta => {
title => blah,
author => foo,
});

$rep->retrieve(tag => groupname, dest => /newdir);
my $data = $rep->get_meta(tag => groupname);

This module is intended to serve as a repository for files, whether those files are local or remote. Different drivers can work independantly to provide differing backing stores. For example, one driver can use a locally-mounted filesystem (even if that is a network filesystem), another could use FTP or HTTP, another could use gmail, and another could use a relational database such as MySQL or DB2.

Drivers may choose to compress the repository, unless explicitly told otherwise.
Keeping this in mind, the API presented here cannot expose things that are not generic to other possible implementations. That said, some possible implementations may not allow adding ("sending" to a web server) - it is expected that they will either throw an exception, or take extra params for FTPing to the server.

CVS History is a Web application for searching the history of CVS actions. It parses the output of the CVS history command and imports it into a MySQL database for ease of manipulation by the PHP front-end.
Its advantage over other CVS history viewing applications is that it only needs anonymous CVS access to the repository.
Main features:
- Tested on Firefox and IE
- XHTML and CSS validated code
- RSS feed of the search query results
- Export the output of search query to other formats (e.g. CSV file)
- Searches can be bookmarked
- History entries can be linked to a ViewVC installation of the same repository

Repository::Simple is a simple hierarchical repository for Perl.

SYNOPSIS

use Repository::Simple;

my $repository = Repository::Simple->attach(
FileSystem => root => /home/foo
);

NOTICE: This software is still in development and the interface WILL CHANGE.
This is the main module of a hierarchical repository system, which is loosely based upon the File::System module Ive written combined with ideas from the JSR 170, a.k.a. Content Repository API for the Java API Specification.

The goal of this package is to provide a content repository system with a similar feature set. I think it would be a good goal to aim for loose compatibility, but it is not my intent to adhere to the strict letter of that standard.

RDF::Sesame::Repository is a repository on a Sesame server.

This class is the workhorse of RDF::Sesame. Adding triples, removing triples and querying the repository are all done through instances of this class. Only SELECT queries are supported at this point, but it should be fairly straightforward to add CONSTRUCT functionality. If you do it, send me a patch.

METHODS

construct ( %opts )
Evaluates a construct query and returns the RDF serialization of the resulting RDF graph. A minimal invocation looks something like:
my $q = qq(
CONSTRUCT {Parent} ex:hasChild {Child}
FROM {Child} ex:hasParent {Parent}
USING NAMESPACE
ex =
);
my $rdf = $repo->construct(
query => $q,
format => turtle,
);

If an error occurs during the construction, an exception is thrown. This is different from some RDF::Sesame methods which return undef.
format

Required: Yes

Indicates the RDF serialization format that the Sesame server should return. Acceptable values are rdfxml, turtle and ntriples.
language

Default: SeRQL

Specifies the language in which the construct query is written. This is only included for forwards-compatibility since the only query language supported by Sesame is SeRQL.

output

Default: undef

Indicates where the RDF serialization should be placed. The default value of undef means that the serialization should simply be returned as the value of the construct method.

If the value is a filehandle, the serialization is written to that filehandle. The filehandle must already be open for writing. Otherwise, the value is taken to be a filename which is opened for writing (clobbering existing contents) and the serialization is written to the file.

query

Required : Yes

The text of the construct query.

extract ( %opts )

Extract an RDF representation of all the triples in the repository. The only required option is "format" which specifies the serialization format of the resulting RDF. The minimal method invocation looks like

my $rdf = $repo->extract( format => turtle )

where $rdf is a reference to a scalar containing the serialization of all the triples in the repository. The streaming results returned by Sesame are handled appropriately so that memory usage in minimized. If the output is sent to a file (see "output"), only one "chunk" is held in memory at a time (subject to caching by your OS). The serialization may also be compressed (or otherwise processed) as its being streamed from the server (see "compress").

Error handling is done differently in this method than in other methods in RDF::Sesame. Namely, if an error occurs, an exception is thrown (rather than returning undef and setting errstr(). Eventually, Id like all methods to behave this way.

HTTP::OAI::Repository is a documentation for building an OAI compliant repository using OAI-PERL.

Using the OAI-PERL library in a repository context requires the user to build the OAI responses to be sent to OAI harvesters.

SYNOPSIS

use HTTP::OAI::Harvester;
use HTTP::OAI::Metadata::OAI_DC;
use XML::SAX::Writer;
use XML::LibXML;

# (all of these options _must_ be supplied to comply with the OAI protocol)
# (protocolVersion and responseDate both have sensible defaults)
my $r = new HTTP::OAI::Identify(
baseURL=>http://yourhost/cgi/oai,
adminEmail=>youremail@yourhost,
repositoryName=>agoodname,
requestURL=>self_url()
);

# Include a description (an XML::LibXML Dom object)
$r->description(new HTTP::OAI::Metadata(dom=>$dom));

my $r = HTTP::OAI::GetRecord->new(
header=>HTTP::OAI::Header->new(
identifier=>oai:myrepo:10,
datestamp=>2004-10-01
),
metadata=>HTTP::OAI::Metadata::OAI_DC->new(
dc=>{title=>[Hello, World!],description=>[My Record]}
)
);
$r->about(HTTP::OAI::Metadata->new(dom=>$dom));

my $writer = XML::SAX::Writer->new();
$r->set_handler($writer);
$r->generate;

Fedora Digital Object Repository is an open source software which gives organizations a flexible service-oriented architecture for managing and delivering their digital content. At its core is a powerful digital object model that supports multiple views of each digital object and the relationships among digital objects.
Digital objects can encapsulate locally-managed content or make reference to remote content. Dynamic views are possible by associating web services with objects. Digital objects exist within a repository architecture that supports a variety of management functions. All functions of Fedora, both at the object and repository level, are exposed as web services. These functions can be protected with fine-grained access control policies.
This unique combination of features makes Fedora an attractive solution in a variety of domains. Some examples of applications that are built upon Fedora include library collections management, multimedia authoring systems, archival repositories, institutional repositories, and digital libraries for education.
Enhancements:
- This is a significant release of Fedora that includes a complete repackaging as a proper Web application.
- A new installer application makes it easy to setup and run.
- It now uses Servlet Filters for authentication.
- The Fedora repository can also be configured to calculate and store checksums for content.
- The RDF-based Resource Index has been tuned for better performance.
- A new high-performing RDBMS-backed triplestore has been developed that can now be plugged into the RI.

ZSRep (Zaurus Synchronization Repository) is a project whose main goal is to provide a professional solution for synchronizing your Sharp Zaurus with any Desktop PIM software on the Linux operating system.
It is designed specifically to work with the newer Sharp ROMs (DTM-based).
Enhancements:
- Implemented Single Action Full Sync.
- Now uses new unique create and destroy identifiers for plugins.
- Added unique create and destroy identifiers to Address Book plugin template.
- Fixed the Todo Notes to Desc translation problem when syncing after a Full Sync.
- Added the Todo CleanUp call to single action Full Sync mode.