Ports Search

ZXID aims at full stack implementation of all federated identity management and identity web services protocols. Initial goal is supporting SP role, followed by ID-WSF WSC and IdP roles. ZXID is light weight, has a small foot print, and is implemented in C. It is suitable for both high performance and embedded applications. Scripting languages are supported using SWIG, including Perl, PHP and Java. The "full stack" nature of ZXID means it's self contained and has minimal external library dependencies (see downloads).

scan_ffs(8) recovers accidential lost or deleted disklabels. This is the life-saver of typos. If you have ever been working too long, and just happened to type 'disklabel -rw da0 floppy', instead of 'diskla- bel -rw fd0 floppy', you know what I am talking about. This little program will take a raw disk device (which you might have to create) that covers the whole disk, and finds all probable UFS/FFS parti- tions on the disk. It has various options to make it go faster, and to print out information to help in the reconstruction of the disklabel. Ported from OpenBSD to FreeBSD 4/5 with support for UFS1 and UFS2.

humanzip is a compression program that operates on text files. Unlike most compression algorithms, its output is human readable. Indeed, it is explictly meant to be read by humans and might even be easier to read than the original. humanzip compresses files by looking for common strings of words and replacing them with single symbols. The idea is to reduce the screen and print size of documents. Humanzip does not explictly try to reduce the size of the file as measured in bytes, although this usually happens incidentally.

The mission of the Scientific and Technical Information Exchange (STIX) font creation project is the preparation of a comprehensive set of fonts that serve the scientific and engineering community in the process from manuscript creation through final publication, both in electronic and print formats. Toward this purpose, the STIX fonts will be made available, under royalty-free license, to anyone, including publishers, software developers, scientists, students, and the general public. These fonts cover all the symbols in MathML and this port can replace the former x11-fonts/mathfonts.

The other benchmark modules provide excellent timing for specific parts of your code. This module aims to allow you to easily time the progression of your code. The stopwatch analogy is that at some point you get a new stopwatch and start timing. Then you note certain events using lap. Finally you stop the watch and then print out a summary. The summary shows all the events in order, what time they occurred at, how long since the last lap and the percentage of the total time. Hopefully this will give you a good idea of where your code is spending most of its time. The times are all wallclock times in fractional seconds. That's it.

spatialite-tools is a collection of open source Command Line Interface (CLI) tools supporting SpatiaLite. * spatialite: a complete CLI front-end, more or less equivalent to the well known sqlite3 front-end, but fully supporting SpatiaLite * spatialite_tool: a tool supporting import/export of Shapefiles and DBF-files * shp_doctor: a diagnostic tool to check anomalous shapefiles * exif_loader: an import tool for EXIF or EXIF-GPS (JPEG) pictures * spatialite_network: a tool creating a VirtualNetwork (supporting shortest path / routing SQL queries) * spatialite_gml: a tool importing GML files * spatialite_convert: a tool converting DB-files from different versions of SpatiaLite * spatialite_dxf: an tool importing DXF files * OSM-tools: spatialite_osm_raw, spatialite_osm_filter, spatialite_osm_map, spatialite_osm_net, spatialite_osm_overpass: tools supporting OpenStreetMap datasets * XML-tools: spatialite_xml_load, spatialite_xml_collapse, spatialite_xml_print, spatialite_xml_validator: tools supporting XML files processing

If you want Emacs to support you in your efforts to define and manage your projects or tasks this Emacs extension is for you. Some of the features you might find useful within the Emacs environment: * Keep track of tasks in multiple projects * Manage your todos * Display Gantt bars for all tasks and todos * Change the zoom factor of the Gantt chart * Classify each project task according to its criticality: o Normal tasks o High risk tasks o Tasks lying on the critical path * Make task and todo notes * Set task-specific progress goals: linear, moderate s-shaped, or s-shaped with tougher requirements for the middle phase and therefore more flexibility towards the planned end * Multilingual (German and English) * Print detailed project status reports * Generate LaTeX output for high-quality Gantt charts

The intention of the nglogc library is to provide an easy to use and powerful logging API with mechanism which allows to cram source codes with log statements at the start of implementation and decide at the level of building or at runtime which statements should be processed. Therefore the log statements could be controlled by various log levels and define switches are available to completely remove the call of the functions at pre-processor time. So it is possible to switch on the logging only if it is necessary or only print selected messages without any changes in the source code. Different publishers are provided also as different formats of outputs to fulfil the requirements for software development.

IO::Event provides an object-based callback system for handling nonblocking IO. The design goal is to provide a system that just does the right thing without the user needing to think about it much. All APIs are kept as simple as possible yet at the same time, all functionality is accesible if needed. Simple things are easy. Hard things are possible. Most of the time file handling syntax will work fine: <$filehandle> and print $filehandle 'stuff'. IO::Event provides automatic buffering of output (with a callback to throttle). It provides automatic line-at-a-time input. After initial setup, call IO::Event::loop(). IO::Event was originally written to use Event. IO::Event still defaults to using Event but it can now use AnyEvent or its own event loop.

pty is a tool to help debug console programs which take the terminal out of canonical mode, by allowing the program being debugged and the debugger to run on separate terminal devices. To use pty, the programmer changes to the terminal device where he or she wishes to interact with the program to be debugged, and at the shell prompt, runs pty with no arguments. Pty will print out the filename of the slave side of the pseudo-terminal it has opened. Inside the debugger, running in another terminal device, one then redirects the program to be debugged's IO to the slave (tty command of gdb). When you are finished using pty, you must manually kill it. When pty starts it prints out its pid.