Ports Search

TkCVS is a Tcl/Tk-based graphical interface to the CVS, and Subversion configuration management systems. It will also help with RCS. The user interface is consistent across Unix/Linux, Windows, and MacOS X. TkDiff is included for browsing and merging your changes. It shows the status of the files in the current working directory, and has tools for tagging, merging, importing, exporting, checking in/out, and other user operations. TkCVS also aids in browsing the repository. For Subversion, the repository tree is browsed like an ordinary file tree. For CVS, the CVSROOT/modules file is read. TkCVS extends CVS with a method to produce a "user friendly" listing of modules by using special comments in the CVSROOT/modules file.

xwpe is a X-window programming environment designed for UNIX systems. It is similar to 'Borland C++' MS-DOS programming IDE environment. xwpe supports many compilers, linkers, and debuggers, so you are not tied to any particular set of tools. There is both a curses and X11 interface (the later with mouse support). Errors that occur while compiling and linking a program can be examined in the sources -- the cursor will jump to the corresponding line in the source file. Programs composed of more than one source file, can be managed with the project-option. Your program may be run and debugged from within xwpe -- allowing the user to set breakpoints and watch variables. Note: there are both English and German language version of the man pages, and help files. The German language version will be installed if "GERMAN_LANG" is set during ``make install'' of the port.

SWIG is a software development tool that connects programs written in C and C++ with a variety of high-level programming languages. SWIG is used with different types of target languages including common scripting languages such as Javascript, Perl, PHP, Python, Tcl and Ruby. The list of supported languages also includes non-scripting languages such as C#, Common Lisp (CLISP, Allegro CL, CFFI, UFFI), D, Go language, Java, Lua, Modula-3, OCAML, Octave and R. Also several interpreted and compiled Scheme implementations (Guile, MzScheme/Racket, Chicken) are supported. SWIG is most commonly used to create high-level interpreted or compiled programming environments, user interfaces, and as a tool for testing and prototyping C/C++ software. SWIG is typically used to parse C/C++ interfaces and generate the 'glue code' required for the above target languages to call into the C/C++ code. SWIG can also export its parse tree in the form of XML and Lisp s-expressions.

libasyncns is a C library for Linux/Unix for executing name service queries asynchronously. It is an asynchronous wrapper around getaddrinfo(3), getnameinfo(3), res_query(3) and res_search(3) from libc and libresolv. In contrast to GNU's asynchronous name resolving API getaddrinfo_a(), libasyncns does not make use of UNIX signals for reporting completion of name queries. Instead, the API exports a standard UNIX file descriptor which may be integerated cleanly into custom main loops. In contrast to asynchronous DNS resolving libraries like libdenise, skadns, adns, libasyncns is just an asynchronous wrapper around the libc's synchronous getaddrinfo() API, which has the advantage of allowing name resolution using techniques like Multicast DNS, LDAP or NIS using standard libc NSS (Name Service Switch) modules. libasyncns is compatible with IPv6 if the underlying libc is. libasyncns is very tiny, consisting of just one header and one source file. It has no dependencies besides libc.

libasyncns is a C library for Linux/Unix for executing name service queries asynchronously. It is an asynchronous wrapper around getaddrinfo(3), getnameinfo(3), res_query(3) and res_search(3) from libc and libresolv. In contrast to GNU's asynchronous name resolving API getaddrinfo_a(), libasyncns does not make use of UNIX signals for reporting completion of name queries. Instead, the API exports a standard UNIX file descriptor which may be integerated cleanly into custom main loops. In contrast to asynchronous DNS resolving libraries like libdenise, skadns, adns, libasyncns is just an asynchronous wrapper around the libc's synchronous getaddrinfo() API, which has the advantage of allowing name resolution using techniques like Multicast DNS, LDAP or NIS using standard libc NSS (Name Service Switch) modules. libasyncns is compatible with IPv6 if the underlying libc is. libasyncns is very tiny, consisting of just one header and one source file. It has no dependencies besides libc.

IRONSIDES is an authoritative DNS server that is provably invulnerable to many of the problems that plague other servers. It achieves this property through the use of formal methods in its design, in particular the language Ada and the SPARK formal methods tool set. Code validated in this way is provably exception-free, contains no data flow errors, and terminates only in the ways that its programmers explicitly say that it can. These are very desirable properties from a computer security perspective. IRONSIDES is not a complete implementation of DNS. In particular, it does not support zone transfers or recursive queries. It does, however, support a sufficient number of DNS records to be useful as an authoritative DNS server for an enterprise.

Unbound is designed as a set of modular components, so that also DNSSEC (secure DNS) validation and stub-resolvers (that do not run as a server, but are linked into an application) are easily possible. Goals: * A validating recursive DNS resolver. * Code diversity in the DNS resolver monoculture. * Drop-in replacement for BIND apart from config. * DNSSEC support. * Fully RFC compliant. * High performance, even with validation enabled. * Used as: stub resolver, full caching name server, resolver library. * Elegant design of validator, resolver, cache modules. o provide the ability to pick and choose modules. * Robust. * In C, open source: The BSD license. * Smallest as possible component that does the job. * Stub-zones can be configured (local data or AS112 zones). Non-goals: * An authoritative name server. * Too many Features.

HT is a file editor/viewer/analyzer for executables. The goal is to combine the low-level functionality of a debugger and the usability of IDEs. We aim towards a perfect hex-editing ability and support of the most important file formats. Support means that HT will be able to correctly display and modify the executable header, image and other extensions specific to the file (import/ export sections, relocations, debugging information etc.). Support will probably include the following file formats: - Win32 portable executables (PE) (good support) - Unix executable and linkable format (ELF) (good support) - DOS standard executables (MZ) (supported) - Win32 linear executables (LE) (supported) - Windows/OS2 "new" executables (NE) (supported) - Unix common object file format (COFF) + DJGPP COFF (supported) - OS2 linear executables (LX) - Microsoft object files (.obj)

This port allows to access CP/M file systems similar to the well-known mtools package, which accesses MSDOS file systems. It contains the followin set of tools: * cpmls - list sorted directory with output similar to ls, DIR, P2DOS DIR and CP/M3 DIR[FULL] * cpmcp - copy files from and to CP/M file systems * cpmrm - erase files from CP/M file systems * cpmchmod - change file permissions * cpmchattr - change file attributes * mkfs.cpm - make a CP/M file system * fsck.cpm - check and repair a CP/M file system (only simple errors can be repaired so far). Some images of broken file systems are provided. * fsed.cpm - view CP/M file system * manual pages for everything including the CP/M file system format All CP/M file system features are supported. Password protection is ignored, but a pseudo file [passwd] contains them decrypted.

LIBDSK is a library for accessing disks and disk image files. It is intended for use in: * Allows CPMTOOLS use of emulator .DSK images. * Emulator tools - converting between real floppy disks and disk images, as CPCTRANS / PCWTRANS do under DOS. * Floppy controller emulation backend * Data transfer from/to real CP/M systems via serial line. LIBDSK has drivers for: Raw files (including /dev/fdn), .DSK files (CPCEMU, JOYCE and other Sinclair/Amstrad emulators), MYZ80 hard drive image, NanoWasp floppy image, .CFI (Compressed Floppy Image, as created by FDCOPY.COM under DOS), Linux floppy drive (supports CPC System and Data formats, which the standard "Raw file" driver does not), Windows 3.x/95/98/ME/NT/2000 floppy drive, DOS floppy drive (via the PC BIOS), CopyQM files (read-only), TeleDisk files (read-only), APRIDISK image files, rcpmfs - makes a Unix/Windows directory appear to be a CP/M disc image.