Ports Search

A small wrapper for libmagic.

Contents of p5-Filter ===================== Filter::sh use Filter::sh 'command' ; This filter pipes the current source file through the program which corresponds to the command parameter using the Bourne shell. Filter::exec use Filter::exec qw(command parameters) ; This filter pipes the current source file through the program which corresponds to the command parameter. Filter::cpp use Filter::cpp ; This source filter pipes the current source file through the C pre-processor (cpp) if it is available.

Find::Lib is a perl helper to smartly find libs to use in the filesystem tree.

Locate and 'use lib' directories along the path of $FindBin::Bin to automate locating modules. Uses File::Spec and Cwd's abs_path to accomodate multiple O/S and redundant symlinks.

File::Map - Memory mapping made simple and safe

This module can be used to determine the mime type of a file. It tries to implement the freedesktop specification for a shared MIME database. For this module shared-mime-info-spec 0.12 was used. This package only uses the globs file. No real magic checking is used. The File::MimeInfo::Magic package is provided for magic typing. If you want to determine the mimetype of data in a memory buffer you should use File::MimeInfo::Magic in combination with IO::Scalar.

The Modified module is intended as a simple method for programs to detect whether configuration files (or modules they rely on) have changed.

File::Path - Create or remove directory trees

This software manages a pid file for you. It will create a pid file, query the process within to discover if it's still running, and remove the pid file.

This defines the policy for file I/O with modules such as File::Slurp::WithinPolicy. The purpose is to allow systems administrators to define locations and restrictions for applications' file I/O and give app developers a policy to follow. Note that the module doesn't ENFORCE the policy - application developers can choose to ignore it (and systems administrators can choose not to install their applications if they do!). You may control which policy gets applied by creating a File::Policy::Config module with an IMPLEMENTATION constant. You may write your own policy as a module within the File::Policy:: namespace. By default (if no File::Policy::Config is present), the File::Policy::Default policy gets applied which doesn't impose any restrictions and provides reasonable default locations for temporary and log files.