Ports Search

The Free Software Foundation's core utilities: basename, cat, chgrp, chmod, chown, chroot, cksum, comm, cp, csplit, cut, date, dd, df, dir, dircolors, dirname, du, echo, env, expand, expr, factor, false, fmt, fold, groups, head, hostid, hostname, id, install, join, kill, link, ln, logname, ls, md5sum, mkdir, mkfifo, mknod, mv, nice, nl, nohup, od, paste, pathchk, pinky, pr, printenv, printf, ptx, pwd, readlink, rm, rmdir, seq, sha1sum, shred, sleep, sort, split, stat, stty, su, sum, sync, tac, tail, tee, test, touch, tr, true, tsort, tty, uname, unexpand, uniq, unlink, uptime, users, vdir, wc, who, whoami, yes Similar utilities to most of these exist in the FreeBSD base system, but many of the GNU versions have added functionality that is useful. Note that this port will install these utilities with a `g' prefix, for example gdate, gexpr, and gtest, but the texinfo documentation will refer to them without the `g' prefix. GNU su does not support a wheel group. This port installs it without the suid bit, unless you define WITH_SUID while building.

XMX is an X protocol multiplexor. It is a standalone utility for displaying an X Windows session on multiple displays. XMX takes advantage of the networked nature of the X Window System by tapping the communication link between an X client and an X server. In this way, XMX works with any X clients and any X servers, without the need to modify either. It's tempting to call this "broadcast software," and that is certainly the effect. In reality, though, XMX is "multicast" software. It must know all the slave machines ahead of time and it connects to each one directly. XMX is more like mail than news. XMX connects to N servers like an X client, then accepts connections from M clients like an X server. One of those servers is designated the "master" from which input is directed to the clients. The other servers are "slaves." Slave servers receive only those protocol requests that are necessary for them to maintain a visual look-alike of the master server's display. This software was developed at Brown University for use in our electronic classroom. Some version of it has been in use here since 1988.

DeaDBeeF (as in 0xDEADBEEF) is an audio player. Main features: - mp3, ogg vorbis, flac, ape, wv, wav, m4a, mpc, cd audio (and many more) - sid, nsf and lots of other popular chiptune formats - ID3v1, ID3v2.2, ID3v2.3, ID3v2.4, APEv2, xing/info tags support - character set detection for non-unicode id3 tags - supports cp1251 and iso8859-1 - unicode tags are fully supported as well (both utf8 and ucs2) - cuesheet (.cue files) support, with charset detection (utf8/cp1251/iso8859-1) - tracker modules like mod, s3m, it, xm, etc - HVSC song length database support for sid - minimize to tray, with scrollwheel volume control - drag and drop, both inside of playlist, and from filemanagers and such - control playback from command line - plugin support; bundled with lots of plugins, such as global hotkeys and last.fm scrobbler; sdk is included - duration calculation is as precise as possible for vbr mp3 files (with and without xing/info tags) - and etc...

This is a text to speech system produced by integrating various pieces of code and tables of data, which are all (I believe) in the public domain. The Oxford Text Archive has for several years maintained copies of several machine-readable dictionaries along with its extensive (if unsystematic) collections of other machine-readable texts. This document gives some further details of the various dictionaries available, and summarises the conditions under which copies of them are currently distributed. The Oxford Text Archive Shortlist (available on request via electronic mail and by FTP) gives up to date brief details of all texts held in the Archive. Send electronic mail to ARCHIVE@VAX.OXFORD.AC.UK. For anonymous FTP, look in the directory ota on ota.ox.ac.uk.

This library package provides several forward error correction (FEC) decoders and accelerated primitives useful in digital signal processing (DSP). Except for the Reed-Solomon codecs, these functions take full advantage of the MMX, SSE and SSE2 SIMD instruction sets on Intel/AMD IA-32 processors and the Altivec/VMX/Velocity Engine SIMD instruction set on the G4 and G5 PowerPC. The library includes Viterbi decoders for the following convolutional codes: rate 1/2 k=7 rate 1/2 k=9 rate 1/6 k=15 ("Cassini") plus two Reed-Solomon encoder-decoders: one optimized for the (255,223) CCSDS standard code a general purpose encoder/decoder for arbitrary RS codes and three low-level 16-bit DSP support routines: signed dot product peak detection sum-of-squares (energy) computation This library is licensed under the "lesser" GNU General Public License.

Copyright 1991 by David A. Curry Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. The author makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. ------------------------------------------------------------------------ This is XPostIt Version 3.3.1 for X11 Releases 4 and 5. XPostIt allows you to create small notes to yourself in windows on the screen, and save them in disk files. This is generally neater than having numerous real Post-it notes stuck all around the edges of your monitor. ------------------------------------------------------------------------ Dave Curry Purdue University Engineering Computer Network West Lafayette, IN 47907 davy@ecn.purdue.edu

Matreshka is an Ada framework to develop information systems. It consists of five major components: League, XML processor, Web framework, SQL access, and the Modeling framework. League: High level abstraction of localization and internationalization. Also provides calendrical calculations, regular expressions, and JSON. XML processor: Sax reader and writer, supports XML 1.0 and 1.1 as well as namespaces. It also has an XML catalogs resolver. Web framework: Supports FastCGI, SOAP 1.2 and has a WSDL to Ada translator. SQL access: Database abstraction of MySQL, Oracle, PostgreSQL, SQLite and Firebird. Modeling framework: provides implementation of Meta Object Facility (MOF) written entirely in Ada. Extension modules assist in the analysis of UML modules and extensions (MOF, OCL, and UML testing profile) and diagram definition.

Data::ObjectDriver is an object relational mapper, meaning that it maps object-oriented design concepts onto a relational database. It's inspired by, and descended from, the MT::ObjectDriver classes in Six Apart's Movable Type and TypePad weblogging products. But it adds in caching and partitioning layers, allowing you to spread data across multiple physical databases, without your application code needing to know where the data is stored. It's currently considered ALPHA code. The API is largely fixed, but may seen some small changes in the future. For what it's worth, the likeliest area for changes are in the syntax for the search method, and would most likely not break much in the way of backwards compatibility.

The Inline module allows you to put source code from other programming languages directly "inline" in a Perl script or module. The code is automatically compiled as needed, and then loaded for immediate access from Perl. Inline saves you from the hassle of having to write and compile your own glue code using facilities like XS or SWIG. Simply type the code where you want it and run your Perl as normal. All the hairy details are handled for you. The compilation and installation of your code chunks all happen transparently; all you will notice is the delay of compilation on the first run. The Inline code only gets compiled the first time you run it (or whenever it is modified) so you only take the performance hit once. Code that is Inlined into distributed modules (like on the CPAN) will get compiled when the module is installed, so the end user will never notice the compilation time.

Roles are composable units of behavior. They are useful for factoring out functionality common to many classes from any part of your class hierarchy. See Moose::Cookbook::Roles::Recipe1 for an introduction to Moose::Role. While combining roles affords you a great deal of flexibility, individual roles have very little in the way of configurability. Core Moose provides alias for renaming methods and excludes for ignoring methods. These options are primarily (perhaps solely) for disambiguating role conflicts. See Moose::Cookbook::Roles::Recipe2 for more about alias and excludes. Because roles serve many different masters, they usually provide only the least common denominator of functionality. To empower roles further, more configurability than alias and excludes is required. Perhaps your role needs to know which method to call when it is done. Or what default value to use for its url attribute. Parameterized roles offer exactly this solution.