Liboop is a low-level event loop management library for POSIX-based
operating systems. It supports the development of modular, multiplexed
applications which may respond to events from several sources. It
replaces the "select() loop" and allows the registration of event
handlers for file and network I/O, timers and signals. Since processes
use these mechanisms for almost all external communication, liboop can
be used as the basis for almost any application.
ok alek@
Eases web-request routing, handling, and response as a half-way front,
half-way page controller. Implemented with specific emphasis on enabling
easy unit/integration testing that doesn't require a browser.
from msf
since KOI8_U doesn't come with the Solaris class files, make sure it is
built in the recompile stage. Reported by Matt Jibson.
- add a useable cacerts file and use that instead of current empty one.
charset portions tested by and okay ian@.
This module provides a fairly low level interface to the BSD kqueue(2)
system call, allowing you to monitor for changes on sockets, files,
processes and signals.
from Srebrenko Sehic <haver at insecure.dk>
--
OMake is a build system designed for scalability and portability.
It uses a syntax similar to make utilities you may have used, but
it features many additional enhancements, such as:
Support for projects spanning several directories or directory
hierarchies. Fast, reliable, automated, scriptable dependency
analysis using MD5 digests, with full support for incremental builds.
Fully scriptable, includes a library that providing support for
standard tasks in C, C++, OCaml, and LaTeX projects, or a mixture
thereof. Full native support for rules that build several files
at once.
OMake provides a uniform interface on Linux/Unix (including 64-bit
architectures), Win32, Cygwin, Mac OS X, and other platforms that
are supported by OCaml.
Active filesystem monitoring, where the build automatically restarts
whenever you modify a source file. This can be very useful during
the edit/compile cycle. A built-in command-interpreter osh that
can be used interactively.
Argtable is an ANSI C library for parsing GNU style command line options
with a minimum of fuss. It enables a program's command line syntax to be
defined in the source code as an array of argtable structs.
From Jasper Lievisse Adriaanse <jasper@nedbsd.nl>
IPython provides a replacement for the interactive Python interpreter
with extra functionality, including persistent input history,
readline-based name completion and comprehensive object
introspection. It also allows easy access to the pdb debugger and
Python profiler, as well as the system shell.
submitted by Will Maier <willmaier at ml1.net>
feedback and ok alek@
--
Mercurial is a distributed version control system which features:
o Extremely high-performance delta-compressed storage scheme.
o Optimized for disk layout and access efficiency.
o Complete cross-indexing of files and changesets.
o Bandwidth and CPU efficient HTTP and SSH sync protocols.
o Distributed development model supports unlimited numbers of
developers.
o Allows arbitrary merging between developer branches.
o Doesn't significantly degrade with large numbers of files or
changesets.
o No waiting for locks!
o SHA1 integrity checking on repository data.
o Append-only storage model with transaction journalling.
o Fast full-repository verification.
Config::Grammar is a Perl module to parse configuration files by
following a grammar, which specifies how the configuration file should
look like. The configuration files are nice to work with for humans
and the error messages are helpful because it tells right away that
for example you are setting a variable which isn't defined.
Config::Grammar supports many advanced features, that you can read
about in its documentation.
obviating need to build with JDK Linux compat (which was i386 only anyway).
Add native_bootstrap pseudo-flavor so you can build with a native Sun JDK if you
have one (tested by building this way using JDK built with default Kaffe-based build).
Work by kurt@, tested by him on i386 and me on amd64. OK kurt@.
Class::Data::Accessor is the marriage of Class::Accessor and
Class::Data::Inheritable into a single module. It is used for creating
accessors to class data that overridable in subclasses as well as in
class instances.
A chained accessor is one that always returns the object when called
with parameters (to set), and the value of the field when called with no
arguments.
This module subclasses Class::Accessor in order to provide the same
mk_accessors interface.
This is pragma to change Perl 5's standard method resolution order from
depth-first left-to-right (a.k.a - pre-order) to the more sophisticated
C3 method resolution order.
Class::Inspector allows you to get information about a loaded class.
Most or all of this information can be found in other ways, but they
arn't always very friendly, and usually involve a relatively high level
of Perl wizardry, or strange and unusual looking code. Class::Inspector
attempts to provide an easier, more friendly interface to this
information.
Module::Find lets you find and use modules in categories. This can be
very useful for auto-detecting driver or plugin modules. You can
differentiate between looking in the category itself or in all
subcategories.
solaris class files to bootstrap the jdk build. this avoids the need for
devel/jdk/1.4 to bootstrap and will provide a way to bootstrap the jdk on
amd64 and sparc64 when kaffe runs there.
- fix a keyboard entry problem when numlock is on
- fixup socket option code similar to FreeBSD & NetBSD
