Free install perl module software for linux

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.

MyCMS perl module provides the MN::CMS Perl module used by the MyCMS.

MyCMS perl module contains Perl object classes to manage the data of MyCMS (such as articles, links, and images).

MN::CMS is a perl module that allows you to manage an Internet
publishing system.#

MyCMS is an extension module of MyNews.

MyCMS introduces the concept of article, author and moderator.

Sdictionary is a cross-platform dictionary project uses own Sdict dictionary format. Sdictionary includes Sdict, the main program and two simple applications: Jotter and Data. Unlike ptkdic or gtkdic no MySQL needed, so you can work with dictionary files directly. Currently it is known to work under UNIX, Win32 and Symbian OS.
Main features:
- Cross-platform, works under UNIX, Win32 and Symbian OS
- Open Source, binary .dct format is also open and described in documentation
- Unicode, all words and articles are stored in UTF-8
- Two index levels: short and full
- Compression for dictionary articles
- Tools to convert from text file to .dct and vice versa under both Win32 and UNIX
- Simple Web Dictionary which is included into package
- C library framework with simple CLI, Win32 binaries are available
- Perl API (Sdict.pm module)
- Simple, but powerful Jotter and Data applications
- Compiler which helps you to create own dictionaries

Test::UseAllModules is a Perl module that uses use_ok() function for all modules MANIFESTed.

SYNOPSIS

# basic use
use strict;
use Test::UseAllModules;

BEGIN { all_uses_ok(); }

# if you have modules thatll fail use_ok() for themselves
use strict;
use Test::UseAllModules;

BEGIN {
all_uses_ok except => qw(
Some::Dependent::Module
Another::Dependent::Module
^Yet::Another::Dependent::.* # you can use regex
)
}

Im sick of writing 00_load.t (or something like that) thatll do use_ok() for every module I write. Im sicker of updating 00_load.t when I add another file to the distro. This module reads MANIFEST to find modules to be tested and does use_ok() for each of them. Now all you have to do is updating MANIFEST. You dont have to modify the test any more (hopefully).

Perl OpenID is a perl module for verifying OpenID identities.
Main features:
- asy-to-use API
- Does not depend on underlying web framework
- Extensive documentaion
- Ready-to-use store implementation
- Test suite
- Licensed under the LGPL
Enhancements:
- This release contains a tested, documented library with support for OpenID extensions and Yadis.
- There are examples for both the consumer and server.

Module::Install::Philosophy Perl module contains the concepts behind Module::Install.

SYNOPSIS

This document describes the personal philosophy behind the creation of CPAN::MakeMaker (the predecessor of Module::Install). The views expressed here belong to Brian Ingerson; if they are not of interest to you, you can safely ignore this document.

The above is obviously a mutation of the monumental speech by great Martin Luther King (http://web66.coled.umn.edu/new/MLK/MLK.html). While the contexts are vastly different, I feel that there are some serious parallelisms.
The CPAN has become a place that is not free of injustice. This situation has arisen not out of directed oppression, but from a failure of our community to keep its tools sharp. It is the culmination of many small decisions made in the name of practicality. This is a sad state for an institution that was created to allow all interested people to contribute equally to the best of their ability.

This assertion is rooted in my personal experience as an author. When I created my first Perl module, Inline.pm, I knew that I had done something important. But how was I to make a dent in vast Perl community?

As a complete unknown in the Perl community, my voice did not travel far. I repeatedly tried to get even an acknowledgment from the gurus familiar with XS. No success. I resorted to sending messages with ridiculous subjects to modules@perl.org. (http://www.xray.mpe.mpg.de/mailing-lists/modules/2000-08/msg00078.html) No response. Through sheer determination and shameless self-promotion I eventually got the word out, and I hope the world is a slightly better place for it.
Since then, Inline has won awards and I have had the privilege to meet almost all of Perls finest. But I still remember the pain of starting out, and want to help invite more people into this wonderful world.

One thing I have learned from experience is that the Perl community (and throw in the Python and Ruby people as well) is a small drop in the vast ocean of programming. Its a giant pot of Java out there; and a sea of C. Perl may not be the biggest fish, but with some care and cunning we could become a much bigger school.

These are the current problems that I see with CPAN and the core modules:

New Modules dont help Older Perls
If I were to guess what percent of all Perl5 installations were at the current release level (5.8.0 in October 2002) I would say 3-5%. That may even be generous. Id say that over 40% of installations might still be at 5.005 or earlier.
The biggest problem with adding a module to the core is that it only helps a small subset of Perl users for a long long time. Worse yet, a good module author will still probably avoid using the core additions as prerequisites, because they want their new module to work as well on 5.005 as on 5.8.
CPAN::MakeMaker should be able to help in this regard. For example, instead of putting Inline.pm into the core for 5.9, I can now effectively get it into the core for every version of Perl that Inline supports.
Author Exclusiveness
Not just anybody can get a module into the core. It seems you have to know people in high places. If I were a brilliant new talent with a great new module, it would have a harder time getting the ear of the pumpking, then if I were, say, Damian Conway. In fact, I probably wouldnt even know where to start.
Reduced Competition
One comment Ive heard from some very good Perl programmers is "Everything important has already been done". Their feeling is that even though a module is suboptimal, it would be a waste of time to write a competing module. Who would use it instead of the one already in the core?
When I write a competing module, I know that I have to make it at least twice as good as the existing one to even get noticed. Thats not a bad thing, but should everybody be forced into that situation?
For example, lets say that you have created a really useful CGI script. Lets also say that it makes use of your own CGI::Special module, because CGI.pm doesnt meet your needs. Even though your script might be generally useful and worth sharing, the fact that it requires a non-standard module can only negatively affect its acceptance. Trying to get general acceptance for the superior CGI::Special module will be harder still.
Core modules are assumed by the general public to be "Best of Breed". While this may be true for some modules at some point in time, it keeps talented people from attempting to "breed" something better.
Core Bloat
Every time we add a module to the core it gets bigger and bigger. And we cant ever remove modules from the core, once theyve been added.
If I had my druthers, wed remove all modules from the core that werent necessary for either running Perl or installing modules. Of course, wed need to set things up so that installing modules was so easy, that it could be done on the fly if necessary. Is this easily accomplishable? Nope. Is it impossible? Nope. We have the best language in the world to help us do it!
Maintenance Bitrot
Believe it or not, Perl authors can sometimes acquire a "Life Beyond Perl". They get families or new hobbies or even hit by a bus. (This would be a "Death Beyond Perl".) The fact is, that once somebody writes a piece of code and shares it with the world, they are expected to maintain it for all time.
That is being generous. There are others that think that once their module has become popular or made it into the core, they dont need to keep fixing and improving it. I have personally been guilty of this sin.
And then theres the Damian Conway Effect. This plagues the exceptional authors who are so innovative and prolific they simply dont have time to maintain everything they have written.

I initially formalized these opinions at the YAPC (Yet Another Perl Conference) in June 2001. Since then I have been trying to think of technological solutions to fix these social problems.

One idea was dubbed NAPC. NAPC is CPAN backwards. It is a large system of precompiled modules that can be installed on the fly, with the goal of reducing the number of modules in the core. NAPC hasnt got started yet. Id still like to do it someday, but its a big problem with a lot of issues.

CPAN::MakeMaker (and now Module::Install) on the other hand, is simple and ultimately flexible. It should work with all of the existing CPAN processes without requiring any changes from them. And new features can be continuously added. Even though it doesnt scratch all of my philosophical CPAN itches, its a good start.

App::Modular is a Perl module with modularization framework for perl programs.
SYNOPSIS
package App::Modular::Module::Test;
use base qw(App::Modular::Module);
sub say_hello {
print "Hello, dear user!";
};
package main;
use App::Modular;
my $modul = instance App::Modular;
$modul->module(Test)->say_hello();
exit;
App::Modular aims to provide a framework which should it make very easy to programmes to create any kind of modular program.
It supports:
- module dependency solving
- autoloading of modules
- event handling (implemented as a contributed App::Modular module)

Perl::Dist::Builder is a Perl module to create win32 Perl installers.

SYNOPSIS

use Perl::Dist::Builder;
my $pdb = Perl::Dist::Builder->new( vanilla.yml );
$pdb->remove_image;
$pdb->build_all;

Perl::Dist::Builder is alpha software.

Perl::Dist::Builder uses a configuration file to automatically generate a complete, standalone Perl distribution in a directory suitable for bundling into an executable installer.

Perl::Dist::Builder requires Perl and numerous modules. See Perl::Dist::Bootstrap for details on how to bootstrap a Perl environment suitable for building new Perl distributions.