Free news archives software for linux

News::Archive is a Usenet news archiving package for downloading and later accessing news articles in bulk.

It can load articles laid out in INN format, retrieve them from a running news server, or just take articles one-by-one. News::Archive module is compatible with News::Web and Net::NNTP::Server, so the articles can be shared either via the Web or via NNTP.

SYNOPSIS

use News::Archive;
my $archive = new News::Archive
( basedir => /home/tskirvin/kiboze );

# Get a news article
my $article = News::Article->new(*STDIN);
my $msgid = article->header(message-id);

die "Already processed $msgidn"
if ($archive->article( $messageid ));

# Get the list of groups were supposed to be saving the article into
my @groups = split(s*,s*, $article->header(newsgroups) );
map { s/s+//g } @groups;

# Make sure were subscribed to these groups
foreach (@groups) { $archive->subscribe($_) }

# Actually save the article.
my $ret = $archive->save_article(
[ @{$article->rawheaders}, , @{$article->body} ], @groups );
$ret ? print "Accepted article $messageidn"
: print "Couldnt save article $messageidn";

News::Archive keeps several files to keep track of its archives:

active file

Keeps track of all newsgroups we are "subscribed" to and all of the information that changes regularly - the number of articles we have archived, the current first and last article numbers, etc.

Watched over with News::Active.

history database

A simple database keeping track of articles by Message-ID. Makes access by ID easy, and ensures that we dont save the same article twice. The database chosen to maintain these is user-determined.

newsgroup file

Keeps track of more static information about the newsgroups we are subscribed to - descriptions, creation dates, etc.

Watched over with News::GroupInfo.

archive directory

Directory structure of all articles, with each article saved as a single textfile within a directory structure laid out at one section of the group name per directory, such as "rec/games/mecha". Crossposts are hardlinked to other directory structures.

Articles are actually divided into sub-directories containing up to 500 articles, to avoid Unix directory size performance limitations. Individual files are thus stored in a file such as "rec/games/mecha/1.500/1".

Each newsgroup also contains overview information, watched over with
News::Overview. This overview file goes in the top of the structure,
such as "rec/games/mecha/.overview".

You may note that these files are very similar to how INN does its work. This is intentional - this package is meant to act in many ways like a lighter-weight INN.

Usage:

Global Variables

The following variables are set within News::Archive, and are global throughout all invocations.

$News::Active::DEBUG
Default value for "debug()" in new objects.

$News::Active::HOSTNAME
Default value for "hostname()" in new objects. Obtained using
"Sys::Hostname::hostname()".

$News::Active::HASH
The number of articles to keep in each directory. Default is 500;
change this at your own peril, since things may get screwed up later
if you change it after archiving any articles!

Archive::Rar is a interface with the rar command.

SYNOPSIS

use Archive::Rar;
my $rar =new Archive::Rar();
$rar->Add(
-size => $size_of_parts,
-archive => $archive_filename,
-files => @list_of_files,
);

This is a module for the handling of rar archives.

Locates the rar command (from PATH or from regedit for Win32) and encapsulate it to create, extract and list rar archives.

At the moment these methods are implemented:

new()

Returns a new Rar object. You can pass defaults options.

Add(%options)

Add file to an archive.

Extract(%options)

Extract the contains of an archive.

List(%options)

Fill the list variable of the object whith the index of an archive.

OPTIONS

-archive

Archive filename.

-files

List of files to add. You can use a scalar value or an array reference.

-quiet

No output for the rar command if True.

-sfx

Create self-extracting archive.

-size

Size of the parts in bytes.

-verbose

Level of verbosity.

Archive::Ar is a Perl interface for manipulating ar archives.

SYNOPSIS

use Archive::Ar;

my $ar = new Archive::Ar("./foo.ar");

$ar->add_data("newfile.txt","Some contents", $properties);

$ar->add_files("./bar.tar.gz", "bat.pl")
$ar->add_files(["./again.gz"]);

$ar->remove("file1", "file2");
$ar->remove(["file1", "file2");

my $filedata = $ar->get_content("bar.tar.gz");

my @files = $ar->list_files();
$ar->read("foo.deb");

$ar->write("outbound.ar");

$ar->DEBUG();

Archive::Ar is a pure-perl way to handle standard ar archives.

This is useful if you have those types of old archives on the system, but it is also useful because .deb packages for the Debian GNU/Linux distribution are ar archives. This is one building block in a future chain of modules to build, manipulate, extract, and test debian modules with no platform or architecture dependence.

You may notice that the API to Archive::Ar is similar to Archive::Tar, and this was done intentionally to keep similarity between the Archive::* modules

Class Methods
new()
new($filename)
new(*GLOB,$debug)

Returns a new Archive::Ar object. Without a filename or glob, it returns an empty object. If passed a filename as a scalar or in a GLOB, it will attempt to populate from either of those sources. If it fails, you will receive undef, instead of an object reference.

This also can take a second optional debugging parameter. This acts exactly as if DEBUG() is called on the object before it is returned. If you have a new() that keeps failing, this should help.
read($filename)
read(*GLOB);

This reads a new file into the object, removing any ar archive already represented in the object. Any calls to DEBUG() are not lost by reading in a new file. Returns the number of bytes read, undef on failure.

read_memory($data)

This read information from the first parameter, and attempts to parse and treat it like an ar archive. Like read(), it will wipe out whatever you have in the object and replace it with the contents of the new archive, even if it fails. Returns the number of bytes read (processed) if successful, undef otherwise.

list_files()
This lists the files contained inside of the archive by filename, as an array.
add_files("filename1", "filename2")
add_files(["filename1", "filename2"])

Takes an array or an arrayref of filenames to add to the ar archive, in order. The filenames can be paths to files, in which case the path information is stripped off. Filenames longer than 16 characters are truncated when written to disk in the format, so keep that in mind when adding files.

Due to the nature of the ar archive format, add_files() will store the uid, gid, mode, size, and creation date of the file as returned by stat();

add_files() returns the number of files successfully added, or undef on failure.
add_data("filename", $filedata)

Takes an filename and a set of data to represent it. Unlike add_files, add_data is a virtual add, and does not require data on disk to be present. The data is a hash that looks like:

$filedata = {
"data" => $data,
"uid" => $uid, #defaults to zero
"gid" => $gid, #defaults to zero
"date" => $date, #date in epoch seconds. Defaults to now.
"mode" => $mode, #defaults to "100644";
}

You cannot add_data over another file however. This returns the file length in bytes if it is successful, undef otherwise.

write()
write("filename.ar")

This method will return the data as an .ar archive, or will write to the filename present if specified. If given a filename, write() will return the length of the file written, in bytes, or undef on failure. If the filename already exists, it will overwrite that file.
get_content("filename")

This returns a hash with the file content in it, including the data that the file would naturally contain. If the file does not exist or no filename is given, this returns undef. On success, a hash is returned with the following keys:

name - The file name
date - The file date (in epoch seconds)
uid - The uid of the file
gid - The gid of the file
mode - The mode permissions
size - The size (in bytes) of the file
data - The contained data
remove("filename1", "filename2")
remove(["filename1", "filename2"])

The remove method takes a filenames as a list or as an arrayref, and removes them, one at a time, from the Archive::Ar object. This returns the number of files successfully removed from the archive.

DEBUG()

This method turns on debugging. Optionally this can be done by passing in a value as the second parameter to new. While verbosity is enabled, Archive::Ar will toss a warn() if there is a suspicious condition or other problem while proceeding. This should help iron out any problems you have while using the module.

Archive::Zip is a Perl module which provides an interface to ZIP archive files.

SYNOPSIS

# Create a Zip file
use Archive::Zip qw( :ERROR_CODES :CONSTANTS );
my $zip = Archive::Zip->new();

# Add a directory
my $dir_member = $zip->addDirectory( dirname/ );

# Add a file from a string with compression
my $string_member = $zip->addString( This is a test, stringMember.txt );
$string_member->desiredCompressionMethod( COMPRESSION_DEFLATED );

# Add a file from disk
my $file_member = $zip->addFile( xyz.pl, AnotherName.pl );

# Save the Zip file
unless ( $zip->writeToFileNamed(someZip.zip) == AZ_OK ) {
die write error;
}

# Read a Zip file
my $somezip = Archive::Zip->new();
unless ( $somezip->read( someZip.zip ) == AZ_OK ) {
die read error;
}

# Change the compression type for a file in the Zip
my $member = $somezip->memberNamed( stringMember.txt );
$member->desiredCompressionMethod( COMPRESSION_STORED );
unless ( $zip->writeToFileNamed( someOtherZip.zip ) == AZ_OK ) {
die write error;
}

The Archive::Zip module allows a Perl program to create, manipulate, read, and write Zip archive files.

Zip archives can be created, or you can read from existing zip files.
Once created, they can be written to files, streams, or strings. Members can be added, removed, extracted, replaced, rearranged, and enumerated. They can also be renamed or have their dates, comments, or other attributes queried or modified. Their data can be compressed or uncompressed as needed.
Members can be created from members in existing Zip files, or from existing directories, files, or strings.

This module uses the Compress::Zlib library to read and write the compressed streams inside the files.

vNews provides a site news script used to relay the latest information regarding any topic to visitors.

vNews is a site news script used to relay the latest information regarding any topic to visitors. And being a part of vScripts, vNews comes with a powerful and flexible administration module where administrators/webmasters can easily change the look of the embedded news to conform with their existing site design.

News Script allows you to write articles for your website. News Script features a WYSIWYG editor which makes writing an article easy and it supports search engine friendly URLs.
Main features:
- Write, edit and delete text articles
- Use the built-in WYSIWYG editor for formatting
- Create search engine friendly URLs
- List and search in existing articles
- Completely template driven
- Installation routine
How the script works
As the admin you can write new articles and list, edit, delete and search in existing ones.
News script features a WYSIWYG editor that gives you full control over the format of an article. JavaScript is required, though. The script allows you to choose an article date and the date when the article is to be published.
The title of an article appears as part of the URL which is good for search engine optimization. In case your server supports mod_rewrite the article URL looks like a normal URL of an HTML page.
On the front end the visitor will be provided with a list of published articles. As admin you can set the number of articles per page which results in several result pages which can be browsed by the visitor.

Jeffs News Aggregator is a news getter / page generator that can pull comics, headlines, and RSS feeds and pump them into your template pages.

WormBase::Archive::Build can create archives of Wormbase releases.

SYNOPSIS

use Bio::GMOD::Admin::Archive;
my $archive = Bio::GMOD::Admin::Archive->new();

$archive->create_archive();

METHODS

Bio::GMOD::Admin::Archive->new(@options)
Create a new WormBase::Archive object for archiving WormBase releases.

The options consist largely of file system and remote paths. If none are provided, they will all be populated from the default file located on the primary WormBase server.

This is the recommended idiom as it insulates your programs from structural changes at WormBase. In this case, archives will be built in /pub/wormbase/RELEASE where RELEASE is a WSXXX release.

There are, however, at least two options that you will wish to provide:

--database_repository Full path where to store archives on your filesystem
--mysql_path Full path to the mysql data dir

See WormBase.pm for additional details on all system-dependent paths that can be overridden.