Free 0.08 software for linux

This is an application to compile assembler files and transfer them from Linux to the XGS (SX28/52 microcontrollers) with the SX-Key.

It requires QT 4, WINE and the SASM assembler. The 0.02 version contains just the transfer part. The newer versions also contain the rest of the IDE to compile the source code and transfer the files.

bgpd.pl is a partial implementation of the BGP protocol (RFC1771) in Perl. It was writen as a tool to monitor BGP routing updates.
bgpd.pl is NOT written to be used as a BGP router in an operational network, in fact is has no support to propogate routing information because there is no code to send BGP UPDATE messages. bgpd.pl also does not touch the routing table of the host it runs on.
tTo install follow these commands:
download and install Net::Patricia from
http://net.doit.wisc.edu/~plonka/Net-Patricia/
cd ; tar zxvf bgpd.pl-0.05.tar.gz
Enhancements:
- One-liner bug fix in handling unknown optional non-transitive attributes (Bug found and fixed by andrew@supernews.net)

Geo::ECEF is a Perl module that converts between ECEF (earth centered earth fixed) coordinates and latitude, longitude and height above ellipsoid.

SYNOPSIS

use Geo::ECEF;
my $obj=Geo::ECEF->new(); #WGS84 is the default
my ($x, $y, $z)=$obj->ecef(39.197807, -77.108574, 55); #Lat (deg), Lon (deg), HAE (meters)
print "X: $xtY: $ytZ: $zn";

my ($lat, $lon, $hae)=$obj->geodetic($x, $y, $z); #X (meters), Y (meters), Z (meters)
print "Lat: $lat tLon: $lon tHAE $haen";

Geo::ECEF provides two methods ecef and geodetic. The ecef method calculates the X,Y and Z coordinates in the ECEF (earth centered earth fixed) coordinate system from latitude, longitude and height above the ellipsoid. The geodetic method calculates the latitude, longitude and height above ellipsoid from ECEF coordinates.

The formulas were found at http://www.u-blox.ch/ and http://waas.stanford.edu/~wwu/maast/maastWWW1_0.zip.

This code is an object Perl rewrite of a similar package by Morten Sickel, Norwegian Radiation Protection Authority

libdoomwad is a library that automates much of the grunt work involved with managing data files for id Softwares game Doom. This is just a library, not a program, so if you are looking for a wad editor, look elsewhere.
Despite Doom being ten years old, quite a few people still play the game and edit maps for it.
I noticed that there is no robust library to manage the low end gruntwork of reading and writing wads, converting binary data into C++ classes and structures for use in editors, etc. so I set out to write my own.
The result is libdoomwad, a cross-platform OS-neutral library to do all these tasks.
Main features:
- Defines structures to represent most of the entries found in wad files.
- Defines a generic Lump class that abstracts a single entry of any type. It handles memory allocation and provides a few useful functions.
- Wad class that abstracts a single wad file. Provides easy file extraction and insertion.
- Consistently uses standard C++ exceptions to provide meaningful, verbose error messages to aid in debugging and to pinpoint exactly what went wrong.
Enhancements:
- Updated documentation. Made the version changes in each file into a pretty list.
- Added LGPL license to Doxygen documentation.
- Added a bunch of warning flags to GCCs command line, then fixed all the warnings that popped up.

MDV::Repsys is a Perl module to build rpm from a svn.

FUNCTIONS

set_verbosity($level)

Set the verbosity verbosity of the module:

0 silent
1 progress message
2 debug message

set_rpm_dirs($dir)

Set internals rpm macros that are used by rpm building functions:
_sourcedir to $dir/SOURCES
_patchdir to $dir/SOURCES
_specdir to $dir/SPECS
create_rpm_dirs

Create directories used by rpm building functions:
_sourcedir
_patchdir
_specdir
Return 1 on sucess, 0 on failure.

extract_srpm($rpmfile, $directory)

Extract (install) a source package into $directory.
find_unsync_files($working_dir, $specfile)

Return two array ref of lists of files that should be added or removed from the svn working copy to be sync with the specfile.

sync_svn_copy($add, $remove)

Perform add or remove of files listed in both array ref.

sync_source($workingdir, $specfile)

Synchronize svn content by performing add/remove on file need to build the package.

$workingdir should a svn directory. No changes are applied to the repository, you have to commit yourself after.

Return 1 on success, 0 on error.

strip_changelog($specfile)

Remove the %changelog section from the specfile.

build($dir, $what, %options)

Build package locate in $dir. The type of packages to build is set in the string $what: b for binaries, s for source.

If $options{specfile} is set, the build is done from this specfile and not the one contains in SPECS/ directory.

Text::Scrub is a Perl module used to wild card out text used for comparison.

SYNOPSIS

#########
# Subroutine Interface
#
use Text::Scrub qw(scrub_date scrub_date_ticket scrub_date_version scrub_file_line
scrub_probe scrub_test_file);

$scrubbed_text = scrub_architect($script_text)
$scrubbed_text = scrub_file_line($script_text)
$scrubbed_text = scrub_date($script_text)
$scrubbed_text = scrub_date_ticket($script_text)
$scrubbed_text = scrub_date_version($script_text)
$scrubbed_text = scrub_probe($script_text)
$scrubbed_text = scrub_test_file($script_text)

#########
# Class Interface
#
use Text::Scrub

$scrubbed_text = Text::Scrub->scrub_architect($script_text)
$scrubbed_text = Text::Scrub->scrub_file_line($script_text)
$scrubbed_text = Text::Scrub->scrub_date($script_text)
$scrubbed_text = Text::Scrub->scrub_date_ticket($script_text)
$scrubbed_text = Text::Scrub->scrub_date_version($script_text)
$scrubbed_text = Text::Scrub->scrub_probe($script_text)
$scrubbed_text = Text::Scrub->scrub_test_file($script_text)

The methods in the Test::STD:Scrub package are designed to support the Test::STDmaker and the ExtUtils::SVDmaker package. This is the focus and no other focus. Since Test::STD::Scrub is a separate package, the methods may be used elsewhere. They are used to wild card out parts of two documents before they are compared by making these snippets the same. In all likehood, any revisions will maintain backwards compatibility with previous revisions. However, support and the performance of the Test::STDmaker and ExtUtils::SVDmaker packages has priority over backwards compatibility.