Free daily build software for linux

The Daily Journal project is a PIM program that is written using the Fast Light Tool Kit.
It manages daily notes, appointments, holidays, contact and to-do lists, and issues alerts before scheduled appointments.
Enhancements:
- Multiple spurious appointment alerts! Traced to wrong starting index in for loop.
- Appt indices should start from 1, instead of zero. Fixed.

Module::Build is a Perl module for build and install Perl modules.

SYNOPSIS

Standard process for building & installing modules:
perl Build.PL
./Build
./Build test
./Build install
Or, if youre on a platform (like DOS or Windows) that doesnt require the "./" notation, you can do this:
perl Build.PL
Build
Build test
Build install

Module::Build is a system for building, testing, and installing Perl modules. It is meant to be an alternative to ExtUtils::MakeMaker. Developers may alter the behavior of the module through subclassing in a much more straightforward way than with MakeMaker.

It also does not require a make on your system - most of the Module::Build code is pure-perl and written in a very cross-platform way. In fact, you dont even need a shell, so even platforms like MacOS (traditional) can use it fairly easily. Its only prerequisites are modules that are included with perl 5.6.0, and it works fine on perl 5.005 if you can install a few additional modules.

Daily strip manager is a simple PHP script which offers more powerful user interface for browsing comic strips, downloaded by DailyStrips perl script, than static html pages.
Daily Strip Manager offers sorting, zooming to specific strip, duplicate control, keyboard navigation (2.0) and more. Nothing much for a quick PHP script, but it works for me.
DS Manager at this time only works with DailyStrips setup configured to put comic strip images in subdirectories using date as a filename (e.g. options -l --stripdir).
Images may actually end with whatever garbage but they MUST start with their full date in format specified in config.php, otherwise nothing would work at all.
You should also enable indexing and provide directory writable by PHP user to store indexes in, otherwise expect general slowness (probably this wont show much on some fancy-shmancy Xeon, but I use P3 as my web server, thank you very much.
DS Manager should itself (with all related files) be placed at the root of your strips collection, otherwise it wont work at all.
As of version 2.0, Daily Strip Manager uses XmlHttpRequest object, which adds dependencies on JavaScript and modern web-browsers (Mozilla flavours and IE6 seem to work fine, dunno about the rest). If you are somehow unhappy with this, use version 1.7 instead.
Enhancements:
- This release adds minor interface improvements.

Build it Fast (BIF) is a PHP Framework. It contains several classes that help you develop complex Web applications in a short amount of time.

It brings the concept of the widget to Web development. It features Cascade Skins and transparent session management.

Its meant to make PHP programers life much easier, and making better web applications.

Module::Build::TestReporter is a Perl module to help users report test failures.

SYNOPSIS

use Module::Build::TestReporter;
my $build = Module::Build::TestReporter->new(
# normal Module::Build code here
);

# or, in your own M::B subclass

package My::Module::Build;

use Class::Roles does => Module::Build::TestReporter;

# your code as usual

Shipping test suites with your code is a good thing, as it helps your users know that your code works as you expect on your systems and it allows you better debugging information if things break in environments where you havent yet tested your code. However, it can be tedious and tricky to convince your users to send you the appropriate failure information.

Module::Build::TestReporter extends and enhances Module::Build to collect information on test failures and the Perl environment for users to send to you. Rather than walking them through running tests in verbose mode on the phone, in IRC, or via e-mail, use this module alongside your usual Module::Build build process and it will gather this information in case of failure.