Free ezpublish modules software for linux

Jeta SSH Module provides a Horde SSH module.

Jeta is the Horde Application Frameworks wrapper module for the SSHTools Java SSH Applet.

Jeta is based on a java SSH client. It allows shell access to your web server, or to another machine if used with a port relay daemon (not provided).

Business::Payroll is a series of Perl Modules that provides an API for working with multiple countries federal, state and local taxes.
Payroll Perl Modules project also supports calculating mileage reimbursement values and can handle adjustment entries.
The Business::Payroll module starts with an xml document in the Input format and if everything is successfull, outputs the results in the Output XML format.
Currently only the US is supported and MO is the only supported state. We are not supporting any cities in MO yet. Federal Income, FICA, Medicare and Mileage Rates are all being calculated. We take into account the number of allowances people can claim and the fact that you can withhold more for federal and state.
Federal Income tables are only available for any date >= 07/01/2001.
See the payroll_test.pl script and input.xml file for a sample implementation.
Use process_payroll (in the /usr/bin directory after an rpm install, otherwise in the payroll-x.y directory) to actually process payroll files for real.
process_payroll will take the specified raw xml file and process it. If no errors occured, then you get the result on stdout. If you specify 2 file names the result will go into the second file. You can specify - (for the first file) and it will know to work with stdin. I.e. you can pipe the file to be processed. Ex. cat input.xml | process_payroll - would process input.xml from the stdin and then output the result to stdout.
Enhancements:
- This release has been updated to cover the 2006 tax changes.

Universal Module Player or UModPlayer, is a audio module "tool-chain", providing you functions to work with modules like playing, exporting, getting information, and more.
Universal Module Player works in UNIX-like platforms, including Linux, Mac OS X, FreeBSD, Solaris...
It uses the Custom LibModPlug audio library, an improved version of the well-known LibModPlug library, supporting more than 20 formats and giving you high playing quality. It uses LibSDL to handle multiplatform sound support.
Main features:
- You can play the supported formats and seek to any order in the song. You have pause, timer, display, and other standard features.
- You can view the pattern notes while playing.
- You can specify noise reduction, megabass, surround, reverb sound options specifying the grade and the delay of most of the options.
- You can create, save and edit playlists to play a selection of modules.
- You can read and export to a file the song builtin message, the song instrument names and the song sample names.
- Each user of your UNIX box can save all the sound options.
- And much more!
Supported Formats
Supported file formats on both Little Endian (Intel x86, etc.) and Big Endian (PowerPC, SPARC, MIPS, Motorola 68000, etc.) platforms:
Impulse Tracker (IT), Scream Tracker (STM), Scream Tracker 3 (S3M), Extended Modules (XM), Amiga Modules (MOD), OktaMED (MED), Oktalyzer (OKT), Unreal Modules (UMX), Composer 669 (669), DigiBooster Pro Modules (DBM), PolyTracker (PTM), and Farandole (FAR)
Additional file formats supported only on Little Endian platforms (support for Big Endian is on development):
MultiTracker Modules (MTM), AFM, AMS, DMF, DSM, DigiTracker (MDL), MadTracker 2.0 (MT2), PSM, ULT
Exporting Formats
You can export or convert any of the above formats to the following file types:
Impulse Tracker (IT)
WAVE Audio File (WAV)
Audio Interchange File Format (AIFF)
Raw Pulse Code Modulation (PCM)
Enhancements:
- Buffer length fixes.
- Playlist commands were a pain. Now we use the first letter of the command name. Also, pressing ENTER does not quit, the user has to explicitly specify to quit pressing q
- Hopefully fixed AIFF exporting bug.
- New section in the README about LibAo configuration, and some misc. rearrangements.

Alien Perl module package contains external libraries wrapped up for your viewing pleasure!

SYNOPSIS

perldoc Alien;

Alien is a package that exists just to hold together an idea, the idea of Alien:: packages, so there is no code here, just motivation for Alien.

Why

James and I ended up doing a build system for Fotango, lots of people have done a build system, it is a pretty boring task. The boring task is really all the mindlessly stupid things you need to do to build C libraries that Perl modules require, these C modules usually have unusual installation systems or require vastly different options. So CPAN modules install easy, 3rd party stuff is nasty.
So, suddenly an idea struck me, Alien packages! Imagine a CPAN module that has as its only task to make sure a certain library is installed! That means that you can write all the voodoo in your Build.PL file and then just make sure the module requires the correct Alien module! Then anything that install Perl modules will deal with it automatically!

How

So, what should an Alien module do? It should make sure that the target is installed and it should provide the caller with enough information to use it.
The idea is that you use it to make sure it is there, and you call class methods to find out what to use. These class methods will be individually specified by the stand alone Alien modules.

No Framework!

The reason this is so loosely worded is because we have no idea what common functionality will be needed, so we will let evolution work for us and see what individual Alien packages need and then eventually factor it out into this packages. I would like to avoid a topdown design approach.

Responsibilities of a Alien module.

On installation, make sure the required package is there, otherwise install it.
On usage, make sure the required package is there, else croak.

Bundle the source with the module, or download it.

Allow module authors to access information it gathers.

Document itself well.

Preferably use Module::Build.

Be sane.

The txObject Python Modules provide an interface to the txObject Application Tool Kit and Libraries. txObject ATK provides both embedded and application level projects a five-layer framework. Each layer offers a unified set of tools that allows programmers to focus their development efforts.
A correlation can be made between txObject ATK and Sun Microsystems Inc. Java Language. txObject ATK has many of the advantages Java has, but without some of the performance issues commonly associated with the Java Language. Javas initial advantages are its platform independent built-in and publicly available support libraries. Due to the basic nature of Java, its libraries have a common object-oriented feel and data flow model. txObject ATK has accomplished a similar Java-like environment for C++.
Another correlation can be made between txObject ATK and the CORBA Standards. As demand increases for applications to run in distributed environments and on multiple platforms, projects have had a new added complexity to their traditional development cycle. txObject ATK greatly decreases such complexity in a similar way CORBA does but with two fundamental differences. The first distinction is that txObject ATK is a tightly coupled peer-to-peer distributed system, where CORBA is a loosely coupled client-server model. The second division is that txObject ATK distributed objects are state and transaction consistent. CORBA provides distributed object interfaces without state.
txObject ATK is ideal for developing embedded applications. It has been optimized for memory and CPU constrained systems. The entire software package is comprised of 5,000 lines of class declaration code and 10,000 lines of implementation code. Further reading shall account for the size of each layer.
Each layer of the txObject ATK is a foundation for every successive layer. In order for a particular layer to operate, it requires the layers below it but not the ones above. Since layer 1 is the base for all other layers, close attention should be paid. Each component in layer 1 will be used intimately throughout layers 2-5.
Main features:
- Layer 1 - Object Library
- Layer 2 - I/O & Timers
- Layer 3 - Object-Oriented Threads
- Layer 4 - Inter-Process Communication
- Layer 5 - True Distributed Object Comm. (Object Replication)

u24mixer-module is a simple kernel module that provides ALSA mixer controls for the ESI U24 USB sound card.
Enhancements:
- All of the mixer controls found in the ESI U24 Windows control panel were implemented.

ProFTPD Quota LDAP module provides a ProFTPD module that imposes quotas based on LDAP user accounts.
This module is designed to impose quotas, on FTP accounts, based on user accounts. It is based on the ideas contained in Eric Estabrooks mod_quota and TJ Saunders mod_quotatab; however, this module has been written from scratch to implement quotas in a very different manner.
Installation
To install mod_quota_ldap, follow these instructions. After unpacking the tarball, copy the mod_quota_ldap.c file into:
{proftpd-dir}/contrib/
after unpacking the latest proftpd-1.2 source code. Follow the usual steps for using third-party modules in proftpd:
$ ./configure --with-modules=mod_quota_ldap make make install
Enhancements:
- Release works with proFTPd-1.2.8 or higher
- Bug#679338 & Bug#679343 - quota_ldap_getconf() bug solved

Drupal::Module::Starter is a Perl module to create Drupal Module starter files.

SYNOPSIS

You probably dont want to use this module directly - you want to use the drupal-module-starter script in the scripts directory of the distribution

use Drupal::Module::Starter;

my $foo = Drupal::Module::Starter->new(path/to/config.yaml);
$foo->generate;
...