Free winrar zip archive software for linux

LinPHA is an easy to use, multilingual, flexible photo/image archive/album/gallery written in PHP. It uses a SQL database to store information about your pictures.

It comes with a HTML based installer, so you dont need experience in setting up SQL DB.

GXMame is a frontend for XMame using the GTK library, the goal is to provide the same GUI than mame32. For the moment it will just have the same gui, the final goal is to be able to share config files with Mame32k (or any version of mame32 that write config files instead of saving data into windows registry) allowing dual booter to have the same environment (favorite, timeplayed, last game selected, gui preference...) under windows and Linux.
I wanted to learn GTK and have a decent frontend for xmame, gnomame didnt work on my computer and I didnt like other front end in Tk, so I decided to start this project, just after I discovered gRustibus, the very good front-end from Kjetil Thuen. I took this front end as a model for the creation of GXMame Im not sure that I could have go so far and so quickly without this model.
Main features:
- Detailed view
- Small icons view
- Indented view (shows clones games under the original one)
- Font color and size selectable
- Icons support, .ico files or a zipped archive from Mamu or Mame32QA
- Tools bar
- Folder(filter) panel
- Screenshot panel
- Display snapshots, Flyers, Marquees, Cabinets, Titles.
- Support of zipped pictures
- Display mameinfo and history
- Status bar
- Support of catver to sort games by version and categories
- Random game selection
- Quick check: only check if a romname.zip file exist in roms folder (also works with clones)
- Audit of all roms
- Window with the properties of all games
- Audit of a single game
- Popup menu to easily access to most used functions
- Preferences for games(global and specific)
- Joystick support (new 386 1.x.x linux driver only)
- Creation of gamelist from xmame
- Multiples executables support
- Scalable icons
- Additionnal options string
- Sortable columns (in any views)
- Sortable selectable columns order (in detail view)
- List view
- Large icons view
- and lot of others...

atool is a script for managing file archives of various types (tar, tar+gzip, zip etc). The main command is probably aunpack, extracting files from an archive.

atool project overcomes the dreaded "multiple files in archive root" problem by first extracting to a unique subdirectory, and then moving back the files if possible. aunpack also prevents local files from being overwritten by mistake.

Other commands provided are apack (create archives), als (list files in archives), and acat (extract files to standard out).

atool identifies archives by their file extension. Sometimes this is not possible, for instance rar archives usually have varying numeric file extensions. In those cases when atool cant identify the format, file(1) is used instead. (atool can also be configured not to use file.)

atool is written in Perl by Oskar Liljeblad (oskar@osk.mine.nu), and is free software (GNU General Public License).

ls4sweep should be used as helper for removing extra old daily-created backups.
Sweeping policy consists from the set of records, where each record contains the count of intervals (or periods) and the length of one period (in days).
ls4sweep checks creation or modification time of given files and displays names of those when they mismatch policy.
Only one file is keeping in each interval.
Consider following command: ls4sweep 3:1,2:3,2:10,2:30,3:90,5:365 *.zip This means:
- keep daily ZIP-archives in current directory for last 3 days
- older than 3 days - keep 2 archives with 3-days delta
- older than 9 days (3*1 + 2*3) - 2 archives with 10-days delta
- older than one month (3*1 + 2*3 + 2+10) - 2 archives with monthly delta
- older than 3 months - 3 archives with 90-days delta
- older than one year - yearly archive for five years
- display filenames of all remaining stuff
ls4sweep output can be directly passed to | xargs -r /bin/rm -f command. When you create archives via cron(8), you can put cleanup via ls4sweep call after creation.
Enhancements:
- A copy of the GPL was added.
- Makefile targets were added for creating tar.gz and rpm packages.
- The source code repository was changed from BitKeeper to SubVersion.

ShowImg is a feature-rich image viewer which can display numerous formats, including JPEG, PNG, GIF (animated), MNG, PSD, ... ShowImg application consists of a tree view frame, a directory and preview frame, and a view frame.
The (larger) view frame can be exchanged with the (smaller) directory/preview frame. It can preview and display images from multiple directories and search for identical images.
ShowImg also features a full-screen mode, zooming, sorting, dragndrop with Konqueror, support for images in compressed archives (tar, tar.gz, zip, ...) and kipi plugins.
Main features:
Viewer
- display JPEG, PNG (alpha layer supported), GIF, XCF, PSD, etc. files;
- open several directories, and archives (.tar.gz, .tar.bz2, .zip, ...);
- apply filters to displayed image;
- preview, fullscreen, slideshow, ``fit-to-screen, efficient zoom;
- open files with external programs;
- support EXIF header (JPEG file metadata);
- display a hexadecimal view.
Management
- batch rename;
- search for exact and similar images;
- several formats conversion;
- manage photo albums.
Configuration
- kipi plugins supported (see kipi plugin homepage);
- configurable interface.
Enhancements:
- Database added to manage images using KexiDB (http://kexi-project.org/),
- Video support added,
- SVG support added,
- RAR archive file support added.

Extended Universal Resource Library is a pure Java library for cleaner, more flexible file access in Java.
How data is stored is completely transparent to the client, since the library is meant to replace java.io.File.
It provides implementations for handling local files, Jar/Zip archives, and XML documents. (Implementations for CVS and FTP are available seperately.) Other storage providers can be written and plugged in.
It also provides a merged filesystem implementation that allows multiple hierarchies to appear as one and to override each other in a controlled way. Other features include notification of changes to files, and support for attaching (dynamically updatable) actions to file objects.
Filesystems are an abstraction on top of java.io.File (in the case of local files), that provide a number of useful things:
- File storage is completely abstracted - third parties can create support for access to file-like objects stored in an arbitrary manner, such as in a database, or in a version control system.
- Built-in support for ZIP/JAR archives and XML-based filesystems and the ability to transparently use other filesystems supported by NetBeans (such as the FTP filesystem) by adding the necessary classes
- Supports listening for change events if a file is externally modified
- Ability to add arbitrary "status" data to a file object and be notified of changes on it
- Support for actions on file objects, allowing you to define what actions are possible on a given file (and dynamically update these), and then expose those actions through your user interface.

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!