Ports Search

[ excerpt from developer's web site ] A Python script to check metalink files and complete a basic download.

[ excerpt from developer's web site ] A cross-platform GUI editor, written in Python. It enables you to both create and edit metalinks in a user friendly fashion. The editor can automatically enter info about file name, file size, hashes & chunk checksums by scanning a local file.

[ excerpt from developer's web site ] Metalink is the main Metalink generation tool. It combines a list of mirrors (from stdin) and a number of files into one Metalink record (stdout). It can also be used to transform a MD5SUMS file into a metalink. Features currently include: - Hashing algorithms: md4 md5 sha1 sha256 sha384 sha512 rmd160 tiger crc32 ed2k gnunet - Generation of Metalink files from MD5SUMS lists

This package provides compatibility locale data for FreeBSD 6.x to run 4.x/5.x binaries. When you have a trouble with locale at running a legacy binary, you should guide them to find legacy locale data with setting PATH_LOCALE environment variable. env PATH_LOCALE=/usr/local/share/compat/locale command

mmv is a program to move/copy/append/link multiple files according to a set of wildcard patterns. This multiple action is performed safely, i.e. without any unexpected deletion of files due to collisions of target names with existing filenames or with other target names.

najitool generates and/or makes altered copies of files in the patterns you specify or shows to the screen. najitool is being developed in the ANSI C standard so it should work and compile on any system that supports ANSI C, which should be every system.

This code provides a function, `i18n-man', with which you can browse UNIX manual pages. Formatting is done in background so that you can continue to use your Emacs while processing is going on. The mode also supports hypertext-like following of manual page SEE ALSO references, and other features. See below or do `?' in a manual page buffer for details. For working with Japanese, English and German, put your dot.emacs file following: (autoload 'jman "i18n-man-ja" nil t) (autoload 'eman "i18n-man-en" nil t) (autoload 'dman "i18n-man-de" nil t) then M-x jman to get a Japanese manual page thru jman(1) and put it in a buffer. M-x eman to get a English manual page thru man(1) and put it in a buffer. M-x dman to get a German manual page thru man(1) and put it in a buffer. If you want byte-compile with your favorite "Emacs", use "byte-comile" script as: # cd /usr/local/share/emacs/site-lisp # /usr/local/share/doc/prom-mew/byte-compile xemacs-mule i18n-man-ja i18n-man-ja.el i18n-man.el For usage of byte_compile scripts, run byte_compile with -h option.

> 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.

nsf - NAKAMURA's Shell Form input utility. This makes a shell script can form-input. Availablity of shell script grow wider and wider.

This implementation of the Unix write program adds many nice features while remaining close to the standard Unix program in spirit. It has been heavily used on M-Net since 1985 and on Grex since 1991, as well as a few other systems. It is a ground-up reimplementation using no proprietary code. It's available under a Berkeley-style license (no charge, no restriction on commercial use, just don't take my name off of it). The current version is fairly portable. Orville write was written for use on M-Net and Grex, both public access Unix systems in Ann Arbor. As such, many of the features are designed to support a system featuring a delicate mix of novice users and hostile pranksters, plus a lot of people who just want to talk. It's user interface is pretty much identical to the normal write program, but it offers many extensions and improvements.