Ports Search

XML::Compile::WSDL11 understands WSDL version 1.1. An WSDL file defines a set of messages to be send and received over (SOAP) connections. This involves encoding of the message to be send into XML, sending the message to the server, collect the answer, and finally decoding the XML to Perl. As end-user, you do not have to worry about the complex details of the messages and the way to exchange them: it's all simple Perl for you. Also, faults are handled automatically. The only complication you have to worry about is to shape a nested HASH structure to the sending message structure. XML::Compile::Schema::template() may help you. When the definitions are spread over multiple files you will need to use addWSDL() (wsdl) or importDefinitions() (additional schema's) explicitly. Usually, interreferences between those files are broken. Often they reference over networks (you should never trust). So, on purpose you must explicitly load the files you need from local disk! (of course, it is simple to find one-liners as work-arounds, but I will to tell you how!)

SpliX is a set of CUPS printer drivers for SPL (Samsung Printer Language) printers. Below is a non-exhaustive list of currently supported printers. Manufacturer Model State Dell 1100 Works Dell 1110 Works Samsung CLP-200 Untested Samsung CLP-300 Works Samsung CLP-500 Works Samsung CLP-510 Works Samsung CLP-550 Works Samsung CLP-600 Untested Samsung CLP-610 Untested Samsung CLX-216X Works Samsung CLX-2170 Untested Samsung CLX-3160 Works Samsung ML-1510 Works Samsung ML-1520 Works Samsung ML-1610 Works Samsung ML-1630 Works Samsung ML-1640 Works Samsung ML-1710 Works Samsung ML-1740 Works Samsung ML-1750 Works Samsung ML-2010 Works Samsung ML-2150 Untested Samsung ML-2250 Works Samsung ML-2251 Works Samsung ML-2510 Works Samsung ML-2570 Works Samsung ML-2550 Works Samsung ML-3050 Untested Samsung ML-3560 Works Samsung SCX-4200 Works Samsung SCX-4500 Works Xerox Phaser 3115 Untested Xerox Phaser 3116 Untested Xerox Phaser 3117 Works Xerox Phaser 3120 Untested Xerox Phaser 3121 Works Xerox Phaser 3122 Untested Xerox Phaser 3130 Works Xerox Phaser 3150 Untested Xerox Phaser 3160 Works Xerox Phaser 3420 Untested Xerox Phaser 3425 Untested Xerox Phaser 5500 Untested Xerox Phaser 6100 Works Xerox Phaser 6110 Works Xerox WorkCentre 3119 Untested

Implementation of a function 'digest()' for the creation of hash digests of arbitrary R objects (using the md5, sha-1, sha-256, crc32, xxhash and murmurhash algorithms) permitting easy comparison of R language objects, as well as a function 'hmac()' to create hash-based message authentication code. The md5 algorithm by Ron Rivest is specified in RFC 1321, the sha-1 and sha-256 algorithms are specified in FIPS-180-1 and FIPS-180-2, and the crc32 algorithm is described in ftp://ftp.rocksoft.com/cliens/rocksoft/papers/crc_v3.txt. For md5, sha-1, sha-256 and aes, this package uses small standalone implementations that were provided by Christophe Devine. For crc32, code from the zlib library is used. For sha-512, an implementation by Aaron D. Gifford is used. For xxHash, the implementation by Yann Collet is used. For murmurhash, an implementation by Shane Day is used. Please note that this package is not meant to be deployed for cryptographic purposes for which more comprehensive (and widely tested) libraries such as OpenSSL should be used.

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.

K3b is a GUI frontend to the CD recording programs cdrdao and cdrecord. It's aim is to provide a very user friendly interface to all the tasks that come with CD and DVD recording. Features so far: * Creating data CDs (on-the-fly, rockridge, joliet, El-Torito) * Creating audio CDs (WAV, MP3, OGG, CD-TEXT; normalization and on-the fly) * Creating Video CDs (VCD 1.1, 2.0, SVCD, CD-i support (Version 4)) * Creating mixed-mode CDs (CD-Extra (CD-Plus, Enhanced Audio CD)) * Creating eMovix CDs * CD Copy (single + multi session, audio, enhanced audio, cloning) * DVD burning (DVD-R(W), DVD+R(W), eMovix, Formatting DVD-RWs and DVD+RWs) * CD Ripping (CDDB support, CD-TEXT reading, several formats) * DVD Ripping and DivX/XviD encoding * Blanking of CDRWs. * Retrieving Table of contents and cdr information. * Writing existing iso images to CD and DVD. * Writing cue/bin files created for CDRWIN * DVD copy (no video transcoding yet) * Enhanced cd device handling (burnfree and justlink support) * KParts plugin

U-Boot loader for Wandboard Solo, Dual, and Quad. Install the u-boot.imx file onto the boot disk using: dd if=u-boot.imx of=/dev/whatever bs=1k oseek=1 conv=sync The U-Boot built by this port expects the first 1MB of the boot media to be reserved for the U-Boot executable and saved environment. The u-boot.imx file begins at an offset of 1K from the start of the boot disk. The U-Boot environment area begins at an offset of 512K. This version is patched so that: * ELF and API features are enabled to support ubldr. * A single U-Boot image supports Solo, Dual[lite], and Quad processors. * When the selected board has multiple SD or MMC devices available, the mmc0 device in U-Boot (and thus the disk0 device in loader(8)) will be whichever device U-Boot was loaded from by the ROM bootloader routines. The sources for this port were originally obtained from commit 87f595d1ee at https://github.com/TechNexion/U-Boot-edm/ which appears to be a slightly modified fork of the stock U-Boot 2013.10 release. As of this writing, the changes in this fork have not been rolled back into upstream U-Boot. For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

RDF.rb is a pure-Ruby library for working with Resource Description Framework (RDF) data. Features: * 100% pure Ruby with minimal dependencies and no bloat. * Fully compatible with RDF 1.1 specifications. * 100% free and unencumbered public domain software. * Provides a clean, well-designed RDF object model and related APIs. * Supports parsing and serializing N-Triples and N-Quads out of the box, with more serialization format support available through add-on extensions. * Includes in-memory graph and repository implementations, with more storage adapter support available through add-on extensions. * Implements basic graph pattern (BGP) query evaluation. * Plays nice with others: entirely contained in the RDF module, and does not modify any of Ruby's core classes or standard library. * Based entirely on Ruby's autoloading, meaning that you can generally make use of any one part of the library without needing to load up the rest. * Compatible with Ruby Ruby 2.x, Rubinius and JRuby 1.7+ (in Ruby 2.0 mode). * Performs auto-detection of input to select appropriate Reader class if one can not be determined from file characteristics.

aria2 is a lightweight multi-protocol & multi-source command-line download utility. It supports HTTP/HTTPS, FTP, BitTorrent and Metalink. aria2 can be manipulated via built-in JSON-RPC and XML-RPC interfaces. Its features include: - Multi-Connection Download. aria2 can download a file from multiple sources/protocols and tries to utilize your maximum download bandwidth. Really speeds up your download experience. - Lightweight. aria2 doesn't require much memory and CPU time. The physical memory usage is typically 4MiB (normal HTTP/FTP downloads) to 9MiB (BitTorrent downloads). CPU usage in BitTorrent with download speed of 2.8MiB/sec is around 6%. - Fully Featured BitTorrent Client. All features you want in BitTorrent client are available: DHT, PEX, Encryption, Magnet URI, Web-Seeding, Selective Downloads and Local Peer Discovery. - Metalink Enabled. aria2 supports The Metalink Download Description Format (aka Metalink v4), Metalink version 3 and Metalink/HTTP. Metalink offers the file verification, HTTP/FTP/BitTorrent integration and the various configurations for language, location, OS, etc. - Remote Control. aria2 supports RPC interface to control the aria2 process. The supported interfaces are JSON-RPC (over HTTP and WebSocket) and XML-RPC.

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.

The tardy program is a tar post-processor. It may be used to manipulate the file headers in tar archive files in various ways. The reason the tardy program was written was because the author wanted to "spruce up" tar files before posting them to the net, mostly to remove artifacts of the development environment, without introducing more. The tardy program was designed to allow you to alter certain characteristics of files after they have been included in the tar file. Among them are: * change file owner (by number or name) * change file group (by number or name) * add directory prefix (e.g. dot) * change file protections (e.g. from 600 to 644) Note that all of these affect ALL files in the archive.