Ports 搜索

S10sh is a USB/serial userspace driver for the Canon PowerShot digital cameras. Using S10sh you can download, upload and explore the images captured with your PowerShot camera. The interface is quite similar to DOS's command.com. S10sh supports the following PowerShot models: G1 (works with USB, not reported if works with the serial interface) G3 (from local patches, perhaps needs further testing/debug) S10 (serial and USB) S20 (serial and USB) S100 aka Digital Ixus (USB only, since it lacks the serial interface) A20 (needs testing) A50 (serial only, supported with problems) Pro70 (serial only, supported with problems) Other models are reported to work as well: Elph S400, Digital Ixus V3, S30, A60, EOS-10D. With the release of libusb 0.1.3b (http://sourceforge.net/projects/libusb/), S10sh gained USB support under FreeBSD. The original author's web page is http://www.kyuzz.org/antirez/s10sh.html

socklog in cooperation with the runit package is a small and secure replacement for syslogd. There are three main features, syslogd provides: - receiving syslog messages from an Unix domain socket (/dev/log) or UDP socket (0.0.0.0:514) and writing them to various files on disk depending on facility and priority. - writing received syslog messages to an UDP socket (a.b.c.d:514) socklog provides these features with the help of runit's runsvdir, runsv, and svlogd, provides a different network logging concept, and additionally does log event notification. svlogd has a built in log file rotation based on file size, so there is no need for any cron jobs or similar to rotate the logs. Log partitions can be calculated properly.

This module provides code coverage metrics for Perl. If you can't guess by the version number this is an alpha release. Code coverage data are collected using a pluggable runops function which counts how many times each op is executed. These data are then mapped back to reality using the B compiler modules. There is also a statement profiling facility which needs a better backend to be really useful. The cover program can be used to generate coverage reports. Statement, branch, condition, subroutine, pod and time coverage information is reported. Statement coverage data should be reasonable, although there may be some statements which are not reported. Branch and condition coverage data should be mostly accurate too, although not always what one might initially expect. Subroutine coverage should be as accurate as statement coverage. Pod coverage comes from Pod::Coverage. Coverage data for path coverage are not yet collected.

XJDIC V2.3, XJDSERVER V2.3 -- (Copyright: J.W. Breen - 1998) XJDIC is an electronic Japanese-English dictionary program designed to operate in the X11 window environment. In particular, it must run in an "xterm" environment which has Japanese language support such as provided by "kterm" or internationalized xterm, aixterm, etc. It is based on JDIC and JREADER which were developed to run under MS-DOS on IBM PCs or clones. XJDIC functions as: (a) an English to Japanese dictionary (eiwa jiten), searching for and displaying entries for key-words entered in English; (b) a Japanese to English dictionary (waei jiten), searching for and displaying entries for keywords or phrases entered in Japanese (kanji, hiragana or katakana); (c) a Japanese-English Character dictionary (kanei jiten), capable of selecting kanji characters by JIS code, radical, stroke count, Nelson Index number or reading, and displaying compounds containing that kanji.

This directory contains three versions of the linuxdoc DTD. The first, original.dtd, is the original untouched DTD from the SGML-tools version 0.99.13 toolkit. The second, freebsd-1.0.dtd, has been slightly modified to (a) remove bogus shortref maps, and (b) add a PART element. The third, freebsd-1.1.dtd adds a manref element. Using the supplied catalog file with James Clark's SP parser, documents beginning like this: <!doctype linuxdoc system> will automatically use the original DTD, while these: <!doctype linuxdoc public "-//FreeBSD//DTD linuxdoc//EN"> <!doctype linuxdoc public "-//FreeBSD//DTD linuxdoc 1.0//EN"> will use the FreeBSD DTD, version 1.0 and this: <!doctype linuxdoc public "-//FreeBSD//DTD linuxdoc 1.1//EN"> will use the FreeBSD DTD, version 1.1. January 17, 1998 jfieber@FreeBSD.org

> There doesn't appear to be any decent way to compare the last modified > times of files from the shell... Before everybody starts inventing their own names for this, it should be noted that V8 already has a program for this, newer(1). It takes two filenames as arguments, and exits with status 0 if and only if either (a) the first exists and the second does not, or (b) both exist and the first's modification time is at least as recent as the second's. Other- wise it exits with non-zero status. (The preceding two sentences are essentially the whole of the manual page for it.) Relatively few people have V8, but in the absence of any other precedent for what this facility should like look, it seems reasonable to follow V8's lead: newer file1 file2 exit with 0 status if file1 exists and file2 does not, or if file1's last modified time is at least as recent as file2's.

A simple, intuitive C++ library to handle JSON serialized data.

A sinatra based gem hosting app, with client side gem push style functionality.

DALMP - Database Abstraction Layer for MySQL using PHP %0 fat, extremely easy to use. Only connect to database when needed. Details * Dependecy Injector (DI) support, load once, trigger when required. * APC, Disk, Memcache, Redis.io cache support. * Group caching cache by groups and flush by groups or individual keys. * Prepared statements ready, support dynamic building queries, auto detect types (i,d,s,b). * Secure connections with SSL. * SQLite3 Encryption. * Save sessions in database (mysql/sqlite) or a cache like redis/memcache/apc. * Easy to use/install/adapt. * Nested Transactions (SAVEPOINT / ROLLBACK TO SAVEPOINT). * Support connections via unix_sockets. * SQL queues. * Export to CSV. * Trace/measure everything enabling the debugger. * Works out of the box with Cloud databases like Amazon RDS or Google cloud. * Lazy database connection. Connect only when needed. * PSR-0 compliance.

BUFR = Binary Universal Form for the Representation of meteorological data. BUFR is approved by WMO (World Meteorological Organization) as the standard universal exchange format for meteorological observations, gradually replacing a lot of older alphanumeric data formats. This module provides methods for decoding and encoding BUFR messages, and for displaying information in BUFR B and D tables and in BUFR flag and code tables. Installing this module also installs some programs: bufrread.pl, bufrresolve.pl, bufrencode.pl, bufr_reencode.pl and bufralter.pl. See https://wiki.met.no/bufr.pm/start for examples of use. For the majority of potential users of Geo::BUFR I would expect these programs to be all that you will need Geo::BUFR for.