Ports 搜索

Term::ReadKey is a compiled perl module dedicated to providing simple control over terminal driver modes (cbreak, raw, cooked, etc.,) support for non-blocking reads, if the architecture allows, and some generalized handy functions for working with terminals. One of the main goals is to have the functions as portable as possible, so you can just plug in "use Term::ReadKey" on any architecture and have a good likelihood of it working.

Shell::EnvImporter allows various kinds of shell scripts (csh, tcsh, bash, zsh and even perl) to be "sourced" into a Perl program. This module also allows restoration of the pre-sourced environment.

This step recreates the MANIFEST by effectively running make manifest, or the equivalent in your build process. I use this as I don't have superfluous files lying around in the distribution directories, and have set the relevant svk ignore properties. To use it, just list in your .shipit file.

Perl interface to various readline packages. If no real package is found, substitutes stubs instead of basic functions.

This module lets you ask the user for a password in the traditional way, from the keyboard, without echoing. This is not intended for use over the web; user authentication over the web is another matter entirely. Also, this module should generally be used in conjunction with Perl's crypt() function, sold separately.

Releasing a new version of software takes a lot of steps... finding the next version number (and making sure you didn't already use that version number before), making sure your changelog is updated, making sure your "make dist" results in a tarball that builds, committing changes (with updated version number), tagging, and uploading the tarball somewhere. Or maybe more steps. Or not some of the above. Maybe you forgot something! And maybe you manage multiple projects, and each project has a different release process. This is all a pain in the ass. You want to be hacking, not jumping through hoops. Your contributors want to see their patches actually make it into a release, which won't happen if you're afraid of releases. shipit automates all the hell. It makes life beautiful.

Sort::Key::DateTime allows to sort objects by some (calculated) key of type DateTime.

The Specio distribution provides classes for representing type constraints and coercion, along with syntax sugar for declaring them. Note that this is not a proper type system for Perl. Nothing in this distribution will magically make the Perl interpreter start checking a value's type on assignment to a variable. In fact, there's no built-in way to apply a type to a variable at all. Instead, you can explicitly check a value against a type, and optionally coerce values to that type. The author's long-term goal is to replace Moose's built-in types and MooseX::Types with this module.

Spoon - A Spiffy Application Building Framework Spoon is an Application Framework that is designed primarily for building Social Software web applications. The Kwiki wiki software is built on top of Spoon. Spoon::Base is the primary base class for all the Spoon::* modules. Spoon.pm inherits from Spiffy.pm. Spoon is not an application in and of itself. (As compared to Kwiki) You need to build your own applications from it.

String::Checker - An extensible string validation module (allowing commonly used checks on strings to be called more concisely and consistently). Why is this useful? If you're only checking one string, it probably isn't. However, if you're checking a bunch of strings (say, for example, CGI input parameters) against a set of expectations, this comes in pretty handy. As a matter of fact, the CGI::ArgChecker module is a simple, CGI.pm aware wrapper for this library.