Free comes from software for linux

Equinox Desktop Environment (shortly EDE) is small desktop environment, builted to be simple and fast.
Comparing to other desktop environments, EDE is much faster and smaller in memory space (EDEs window manager use less memory than xterm).
The word "equinox" comes from the Latin for "equal night". The equinoxes in March and September are the two occasions each year when the day and the night are of equal duration.
For measuring the length of a day, sunrise is the moment when the sun is half-above the horizon and sunset is the moment when the sun is half-under the horizon. Using this definition, the length of the day (and the night) is precisely 12 hours at an equinox.
Main features:
- desktop with icons and wallpaper;
- Xft font anti-aliasing;
- taskbar with configurable menu, cpu status, easy keyboard switching;
- theming;
- localization;
Graphical front-end for:
- xscreensaver configuration;
- software installation (.rpm, .deb, .tgz);
- time and time-zone configuration;
- fast file and directory serch utility;

XMLParser is a library that assists in parsing XML documents into generic PHP arrays. It also comes with RSSParser, an extension of XMLParser that creates simple RSS-specific array structures from RSS feeds.

Devel::Cover package contains code coverage metrics for Perl.

SYNOPSIS

perl -MDevel::Cover yourprog args
cover

perl -MDevel::Cover=-db,cover_db,-coverage,statement,time yourprog args
To test an uninstalled module:
cover -delete
HARNESS_PERL_SWITCHES=-MDevel::Cover make test
cover
To test an uninstalled module which uses Module::Build (0.26 or later):
./Build testcover
If the module does not use the t/*.t framework:
PERL5OPT=-MDevel::Cover make test

This module provides code coverage metrics for Perl. Code coverage metrics describe how throroughly tests exercise code. By using Devel::Cover you can find areas of code not exercised by your tests and find out which tests to create to increase coverage. Code coverage can be considered as an indirect measure of quality.

If you cant guess by the version number this is an alpha release.
Code coverage data are collected using a pluggable runops function which counts how many times each op is executed. These data are then mapped back to reality using the B compiler modules. There is also a statement profiling facility which needs a better backend to be really useful.

The cover program can be used to generate coverage reports.

Statement, branch, condition, subroutine, pod and time coverage information is reported. Statement coverage data should be reasonable, although there may be some statements which are not reported. Branch and condition coverage data should be mostly accurate too, although not always what one might initially expect. Subroutine coverage should be as accurate as statement coverage. Pod coverage comes from Pod::Coverage. If Pod::Coverage::CountParents is available it will be used instead. Coverage data for path coverage are not yet collected.

The gcov2perl program can be used to convert gcov files to Devel::Cover databases.

You may find that the results dont match your expectations. I would imagine that at least one of them is wrong.

The most appropriate mailing list on which to discuss this module would be perl-qa. Discussion has migrated there from perl-qa-metrics which is now defunct. See http://lists.perl.org/showlist.cgi?name=perl-qa.

DKMS comes from Dynamic Kernel Module Support and is a framework where device driver source can reside outside the kernel source tree so that it is very easy to rebuild modules as you upgrade kernels.
This allows Linux vendors to provide driver drops without having to wait for new kernel releases (as a stopgap before the code can make it back into the kernel), while also taking out the guesswork for customers attempting to recompile modules for new kernels.
For veteran Linux users it also provides some advantages since a separate framework for driver drops will remove kernel releases as a blocking mechanism for distributing code.
Enhancements:
- Version comparison for all 2.6 kernels has been fixed.
- README.dkms has been added to %doc.

Castore comes from CApitalization & STORagE and takes place in a user-centered design approach to build an open archive platform, planned to create institutional repositories, managed by librarians in their respective institutions.

With this system, the authors are able to store, convert (XML), fully index, manage, perpetuate, valorize, and distribute their digital documents.

It uses an assembly of components (Tomcat, OO, JDO, Saxon, Lucene, etc.) to build middleware applications, relying on XML and any relational database.

The system has been developed with a component architecture (J2EE) to be able to integrate the platform with any intranet environment with the minimum cost of development.