Free legacy software for linux

We have always dreamed of DOOM sources being released! How much days have we been talking about the features wed put in it.

In the middle of 1997, we heard a rumour that the sources of DOOM would be released. Some months later the miracle happened: during December 1997, id Software made the full source code of DOOM public.

KEEP THE BEST OF DOOM: Simple and fast. We wont add a thousands options that complicate the game and make the deathmatch slow down.
NO CHANGE TO THE GAMEPLAY: At least there will be an original gameplay mode.
USER FRIENDLY AND AIMED AT THE PLAYERS: We do Legacy for the people who PLAY and enjoy DOOM today. We wont make an adventure game out of DOOM, damn!
NO CHEATS IN MULTIPLAYER.

The Black Legacy is an online RPG game project that uses OpenGL and the SDL libraries.
Enhancements:
- The game style was changed.
- A full playable level, volumetric weapons, ray casting collision, optimized collision using OBB+Ray cast, character rotation on shot mode, two animations per character at a time, blood, shields, gun properties, and a compass were added.

File::Backup is a Perl module for easy file backup & rotation automation.

SYNOPSIS

use File::Backup;

backup( from => "/source/path", to => "/destination/path" );
backup( from => "/kansas/*", to => "/oz" );

purge_backups(
to => "/destination/path",
compress => 0,
keep => 5,
timeformat => "YYYYMMDD_hhmmss",
);

This legacy module implements archival and compression (A.K.A "backup") and file rotation and is an implementation of tar and gzip calls.

SugarCRM project is the premier commercial open source customer relationship management application provider, breaking the rules set by conventional CRM solutions.
The limitations of traditional CRM software can be summarized by the lack of flexibility, high costs, and closed-source structure which is embedded into the traditional product offerings. This has led to a failure rate of over 70% with traditional CRM implementations.
SugarCRM provides a powerful solution built on a pure open source stack, offering functionality constructed by the best open source CRM experts from around the world. The Sugar Suite is SugarCRMs vanguard CRM solution that understands todays business demands.
SugarCRM provides a complete set of solutions to deliver the best CRM solution based on your needs. These include:
Main features:
- Low acquisition cost
- Low total cost of ownership (TCO)
- Fast and easy user adoption
- Flexible solution to blend with current business processes
- Open standards for low cost integration with legacy systems

libGlass is a library for distributed computing that makes its programming easy.
The Glass framework is a scalable set of components that can be used by applications to perform distributed computing. Applications are built reusing the available components as needed.
One of the major goals of libGlass is to be a user-friendly framework, not only suitable for new applications, but also for legacy code.
This is an important feature, as most available solutions for distributed computing require a substantial amount of rewrite of legacy code; some of them require a complete change of the application design.
libGlass was designed to achieve the following goals:
- User transparency: the library must be as transparent as possible. Any tasks that are repetitive or that can be done automatically should be done by the library, without user intervention.
The API (Application Programmers Interface) should be simple and intuitive, with a smooth learning curve and provide high level primitives that can be easily used to solve any problems. Legacy code should be easy to port.
- Extensibility: the library must be easily extensible, requiring no recompilation or any other modification to support new features; they must work as plug-ins.
- Performance and efficiency: since the library is for distributed computing, it has to be efficient, consuming as little processing time as possible.
- Network protocol independence: an abstraction layer makes it possible to change the underlying network protocols easily. The application can use the network protocol most efficient for its needs.
- Portability and interoperability: heterogeneous clusters and grid computing being every day more common, the library must be not only portable, but allow different architectures to interoperate seamlessly, something that is not true for most implementations of distributed computing solutions.
- Scalability: there is no use for a distributed solution that does not scale well. Glass has to work well in all sorts of environments, from small clusters to huge grids, and be able to adapt itself to achieve best results.
- Reconfigurable network architecture: most existing solutions are based on a fixed network architecture, usually Master/Slave or Client/Server.
Given the requirements of scalability and performance, and the fact that peer-to-peer applications are everyday more common, its unreasonable to fix the network architecture: the developer should be free to define how nodes will connect with each other.
- Reliability and fault tolerance: distributed computing often requires reliability. Its not acceptable that the misbehavior or crash of a single node crashes the entire computation.
As clusters grow in size and grid computing becomes more common, the MTBF (Mean Time Between Failures) shrinks to a point that it cannot be ignored.
libGlass must be able to handle node crashes gracefully, keeping the application running and avoiding deadlocks and other problems that could arise from the node crash. Nodes should be allowed to join or leave at anytime.
- Thread support: the library must be completely thread-safe.
With clusters of symmetric multiprocessors (SMP) computers becoming more common and new technologies such as HyperThreadingTM, its unacceptable for a distributed computing framework to have thread issues.
Main features:
Plugins:
- Synchronous shared memory
- Distributed asynchronous events
- Synchronization barriers
- Remote aliases
Protocols:
- TCP/IP
- UDP/IP (unfinished)
Architectures:
- Client/Server
- Pure peer to peer (planned)
- Hierarchical (planned)
- Anonymous peer to peer (planned)
Bindings for:
- Java (mostly finished)
Enhancements:
- Fixed packaging problems that could abort compilation

VietPad is a full-featured Java/.NET Vietnamese Unicode text editor. Open, edit, convert, print, and save Vietnamese text-based files in Unicode formats.
Main features:
- Multi-platform
- Windows
- Solaris
- Linux/Unix
- Mac OS X
- Others
- Unicode compatibility
- Read/Write UTF-8 and UTF-16 formats
- Common Vietnamese input methods
- VNI
- VIQR
- Telex
- Unicode Precomposed (NFC) conversion support for Vietnamese legacy (VNI, VPS, VISCII, VIQR, or TCVN3), Numeric Character References (NCR), UTF-8, and Unicode Composite (Decomposed or NFD) formats
- Full localization
- Sort Vietnamese words
- Vietnamese spell check
- Add/Strip/Normalize diacritics
- Undo/Redo edit
- Find/Replace
- Change case
- Remove line breaks
- Shorthand
- Auto-detect file encoding
- Font preview
- Printing
- File & Text Drag-and-Drop capability
- Look & Feel for different operating systems

Module::Install is a standalone, extensible Perl module installer.

SYNOPSIS

In your Makefile.PL: (Recommended Usage)
# Load the Module::Install bundled in ./inc/
use inc::Module::Install;

# Define metadata
name Your-Module;
all_from lib/Your/Module.pm;

# Specific dependencies
requires Carp => 0;
requires File::Spec => 0.80;
build_requires Test::More => 0.42;
recommends Your::OtherModule => 0.01;

no_index directory => demos;

install_script bin/myscript;

auto_install;
WriteAll;

Quickly upgrade a legacy ExtUtil::MakeMaker installer:

# Drop-in replacement to ExtUtils::MakeMaker
use inc::Module::Install;
WriteMakefile( ... );

A dummy Build.PL so we can work with Module::Build as well:

# Dear Distribution Packager. This use of require is intentional.
# Module::Install detects Build.PL usage and acts accordingly.
require Makefile.PL;

Module::Install is a package for writing installers for CPAN (or CPAN-like) distributions that are clean, simple, minimalist, act in a strictly correct manner with both the ExtUtils::MakeMaker and Module::Build build systems, and will run on any Perl installation version 5.004 or newer.

The intent is to make it as easy as possible for CPAN authors (and especially for first-time CPAN authors) to have installers that follow all the best practices for distribution installation, but involve as much DWIM (Do What I Mean) as possible when writing them.