this took a lot of debugging (on sparc64 where it breaks) for such a stupid bug.
pointed out by henning
(and i'm going to go and fix more of those after i relax)
- add snmp FLAVOR from Joel CARNAT <joel at carnat dot net>
- add some auth types and auth/acl helpers
- add NTLM auth SMB patch even though the default port does NOT compile this support in
oggtag is a tiny command-line editor for description tags in Ogg Vorbis
files. It can set all the tags suggested by the Ogg Vorbis specification[1]
on one or several files at a time.
[1] http://www.xiph.org/ogg/vorbis/doc/v-comment.html
Submitted and maintained by Julian Leyh <oenone /at/ oenone.de>
tla is an Arch CLI written in C.
Arch is a revision control system, i.e. a system that makes it easy to
track changes to computer files, mostly the source code to complex
software systems.
It has the following features that set it apart from other revision
control systems, such as CVS, Subversion or Bitkeeper:
- distributed repositories
- advanced merging capabilities
- low barrier of entry : everybody can easily publish their changes to
others projects. Repositories can be hosted on HTTP, FTP SFTP and
WebDav server.
- renames handled
- archive signing and integrity checking : a facility by which the
integrity of a publicly accessible archive can be verified.
Submitted and maintained by Laurent Cheylus <foxy ta free tod fr>
Embedding tests allows tests to be placed near the code its testing.
This is a nice supplement to the traditional .t files. It's like XUnit,
Perl-style.
This is a simple developer's tool for finding circular references in
objects and other types of references. Because of Perl's reference-count
based memory management, circular references will cause memory leaks.
Assertions are the explict expressions of your assumptions about the
reality your program is expected to deal with, and a declaration of
those which it is not. They are used to prevent your program from
blissfully processing garbage inputs (garbage in, garbage out becomes
garbage in, error out) and to tell you when you've produced garbage
output.
When you're writing unit tests for code that deals with tainted data,
you'll want to have a way to provide tainted data for your routines to
handle, and easy ways to check and report on the taintedness of your
data, in standard Test::More style.
