Ports Search

Junicode is an advanced Unicode font for medieval scholars, including the full range of characters for languages written in the Latin script. It also mostly implements the recommendation of the Medieval Unicode Font Initiative (MUFI). The following languages are fully supported: Old and Middle English, Old Icelandic, Runic, Latin, Gothic and Sanskrit transliterations, IPA (International Phonetic Alphabet) and Greek (based on the Greek Double Pica cut by Alexander Wilson of Glasgow in the eighteenth century). Junicode supports the following OpenType features: f and long-s ligatures, contextual and stylistic alternates (calt, salt), horizontal kerning (kern), discretionary ligatures (circled numbers and letters via dlig), MUFI historical ligatures (hlig), glyph (de)composition (ccmp), correct positioning of combining marks -- mark-to-base (mark) and mark-to-mark (mkmk), small caps (smcp and c2sc), old-style figures (onum), super- and subscript numbers (sups and subs), Unicode fractions (frac), swashes (swsh) and mirrored runes (rtlm). Junicode's OpenType style sets provide support for Nordic and Insular letter-forms, Old English typography, enlarged minuscules, E caudata, alternate yogh, MUFI's overlined/deleted characters and many more.

mod_backtrace is an experimental module for Apache httpd 2.x which collects backtraces when a child process crashes. Currently it is implemented only on Linux and FreeBSD, but other platforms could be supported in the future. Requirements: Apache httpd >= 2.0.49 must be built with the --enable-exception-hook configure option and mod_so enabled. Activating mod_backtrace: 1. Load it like any other DSO: LoadModule backtrace_module modules/mod_backtrace.so 2. Enable exception hooks for modules like mod_backtrace: EnableExceptionHook On 3. Choose where backtrace information should be written. If you want backtraces from crashes to be reported some place other than the error log, use the BacktraceLog directive to specify a fully-qualified filename for the log to which backtraces will be written. Note that the web server user id (e.g., "nobody") must be able to create or append to this log file, as the log file is

POPFile is an automatic mail classification tool. Once properly set up and trained, it will scan all email as it arrives and classify it based on your training. You can give it a simple job, like separating out junk e-mail, or a complicated one -- like filing mail into a dozen folders. Think of it as a personal assistant for your inbox. Since v0.21.0, POPFile supports multiple user with a single instance. Using ${LOCALDIR}/sbin/popfile.sh, you can start your own POPFile easily; it uses ${HOME}/.popfile as a working directory. Note for old POPFile users: copy messages/ and corpus/ directory to your ${HOME}/.popfile directory (if not, create it), then start popfile.sh.

Games::Dice simulates die rolls. It uses a function-oriented (not object-oriented) interface. No functions are exported by default. The number and type of dice to roll is given in a style which should be familiar to players of popular role-playing games: adb[+-*/b]c. a is optional and defaults to 1; it gives the number of dice to roll. b indicates the number of sides to each die. % can be used instead of 100 for b; hence, rolling 2d% and 2d100 is equivalent. roll simulates a rolls of b-sided dice and adds together the results. The optional end, consisting of one of +-*/b and a number c, can modify the sum of the individual dice. +-*/ are similar in that they take the sum of the rolls and add or subtract c, or multiply or divide the sum by c. (x can also be used instead of *.) Using b in this slot is a little different: it's short for "best" and indicates "roll a number of dice, but add together only the best few". For example, 5d6b3 rolls five six- sided dice and adds together the three best rolls.

The package consists of two programs - PortRedorector and PortTest. PortRedirector is a daemon that runs telnet to the remote port of the terminal server and redirects its input and output to a virtual terminal device (/dev/pty*). The corresponding slave device (dev/tty*) then can be used by an application that expects a local async terminal port. For example, to monitor a UPS (connected to AUX ports on a Cisco router) using nut. Whenever telnet subprocess terminates on any reason, it is restarted as soon as any data received from the terminal device. It can also work when authentication is required, i.e. it can pass username and password specified in its configuration file. PortTest is something like cu(1). You can use either of them to test the connection.

The premise of basic-prelude is that there are a lot of very commonly desired features missing from the standard Prelude, such as commonly used operators (<$> and >=>, for instance) and imports for common datatypes (e.g., ByteString and Vector). At the same time, there are lots of other components which are more debatable, such as providing polymorphic versions of common functions. So basic-prelude is intended to give a common foundation for a number of alternate preludes. The package provides two modules: CorePrelude provides the common ground for other preludes to build on top of, while BasicPrelude exports CorePrelude together with commonly used list functions to provide a drop-in replacement for the standard Prelude. Users wishing to have an improved Prelude can use BasicPrelude. Developers wishing to create a new prelude should use CorePrelude.

Lexical::Import allows functions and other items, from a separate module, to be imported into the lexical namespace (as implemented by Lexical::Var), when the exporting module exports non-lexically to a package in the traditional manner. This is a translation layer, to help code written in the new way to use modules written in the old way. A lexically-imported item takes effect from the end of the definition statement up to the end of the immediately enclosing block, except where it is shadowed within a nested block. This is the same lexical scoping that the my, our, and state keywords supply. Within its scope, any use of the single-part name of the item (e.g., "$foo") refers directly to that item, regardless of what is in any package. Explicitly package-qualified names (e.g., "$main::foo") still refer to the package. There is no conflict between a lexical name definition and the same name in any package. This mechanism only works on Perl 5.11.2 and later. Prior to that, it is impossible for lexical subroutine imports to work for bareword subroutine calls. (See "BUGS" in Lexical::Var for details.) Other kinds of lexical importing are possible on earlier Perls, but because this is such a critical kind of usage in most code, this module will ensure that it works, for convenience. If the limited lexical importing is desired on earlier Perls, use Lexical::Var directly.

This perhaps ridiculous-seeming module was created to test routines that manipulate random numbers by providing a known output from rand. Given a list of seeds with srand, it will return each in turn. After seeded random numbers are exhausted, it will always return 0. Seed numbers must be of a form that meets the expected output from rand as called with no arguments -- i.e. they must be between 0 (inclusive) and 1 (exclusive). In order to facilitate generating and testing a nearly-one number, this module exports the function oneish, which returns a number just fractionally less than one. Depending on how this module is called with use, it will export rand to a specified package (e.g. a class being tested) effectively overriding and intercepting calls in that package to the built-in rand. It can also override rand in the current package or even globally. In all of these cases, it also exports srand and oneish to the current package in order to control the output of rand. Alternatively, this module can be used to generate objects, with each object maintaining its own distinct seed array.

This module provides basic functions used in descriptive statistics. It borrows very heavily from Statistics::Descriptive::Full (which is included with Statistics::Descriptive) with one major difference. This module is optimized for discretized data e.g. data from an A/D conversion that has a discrete set of possible values. E.g. if your data is produced by an 8 bit A/D then you'd have only 256 possible values in your data set. Even though you might have a million data points, you'd only have 256 different values in those million points. Instead of storing the entire data set as Statistics::Descriptive does, this module only stores the values it's seen and the number of times it's seen each value. For very large data sets, this storage method results in significant speed and memory improvements. In a test case with 2.6 million data points from a real world application, Statistics::Descriptive::Discrete took 40 seconds to calculate a set of statistics instead of the 561 seconds required by Statistics::Descriptive::Full. It also required only 4MB of RAM instead of the 400MB used by Statistics::Descriptive::Full for the same data set.

Mason is a tool for building, serving and managing large web sites. Its features make it an ideal backend for high load sites serving dynamic content, such as online newspapers or database driven e-commerce sites. Mason's various pieces revolve around the notion of "components". A component is a mix of HTML, Perl, and special Mason commands, one component per file. So-called "top-level" components represent entire web-pages, while smaller components typically return HTML snippets for embedding in top-level components. This object-like architecture greatly simplifies site maintenance: change a shared component, and you instantly changed all dependant pages that refer to it across a site (or across many virtual sites). Mason's component syntax lets designers separate a web page into programmatic and design elements. This means the esoteric Perl bits can be hidden near the bottom of a component, preloading simple variables for use above in the HTML. In our own experience, this frees content managers (i.e., non-programmers) to work on the layout without getting mired in programming details. Techies, however, still enjoy the full power of Perl.