Free package software for linux

Kpackage project is a KDE tool for installing, viewing and uninstalling packages.

The formats supported include RPM, Debian, Slackware and BSD package manager.

KPackage is part of the KDE project.

KPackage can be found in the kdeadmin package.

RPM Package Maker is a frontend for other linux tools in order to help linux users to create RPM packages quickly and easily.
Since version 0.8 minimal spec files are kept in:
/usr/src/packages/SPECS/mini
Enhancements:
- Small improvements and bugfixes

Debian::Package::HTML is a Perl module that generates a webpage information (and Linda/Lintian checks) about a Debian binary or source package using HTML::Template

SYNOPSIS

use strict;
use Debian::Package::HTML;
my $package = Debian::Package::HTML->new(%packageHash);
$package->output(%contextHash);

This module outputs a webpage using HTML::Template templates which resumes the information of a normal build environment for a package in Debian (source files, binary packages and changelogs) using Linda/Lintian for sanity checks. It is useful for making unified presentation webpages for those packages which are being sponsorized by someone in Debian.

The Smart Package Manager project has the ambitious objective of creating smart and portable algorithms for solving adequately the problem of managing software upgrading and installation.
This tool works in all major distributions, and will bring notable advantages over native tools currently in use (APT, APT-RPM, YUM, URPMI, etc).
Notice that this project is not a magical bridge between every distribution in the planet. Instead, this is a software offering better package management for these distributions, even when working with their own packages.
Using multiple package managers at the same time (like rpm and dpkg) is possible, even though not the software goal at this moment.
This project is in beta testing. Please, understand that bugs are expected to be found at that stage, and there are features that still must be implemented in the forthcoming future. Even then, this project is being tested in a considerable number of machines for several months already.
Enhancements:
- A channel --remove-all option was added.
- A bug that made the rpm-metadata loader ignore explicitly provided files in certain situations was fixed.
- A detectsys.py plugin was added, which will automatically detect and include system channels when theyre missing.
- Double conversion of paths in LocalMediaHandler is now avoided.
- German translations were integrated and the French translations were merged.
- The deb backend now uses an underline for the name/version separator.
- A bug in the protected read code for old Python versions was fixed along with a locking issue in the RPM pm

GIMP Animation Package is a collection of Plug-Ins to extend the GIMP with capabilities to edit and create Animations as sequences of single frames.

Please note that gimp-gap 2.2.1 requires gimp 2.2 and glib 2.8 or higher. It is recommended to use gtk+ 2.8.

Additional Installation Notes:

This GIMP-GAP release includes sourcecode tarballs of external libraries :

- ffmpeg
- libmpeg3

Those libs are built automatically. Configuration options for those libs can be set by editing the
files:

extern_libs/configure_options_ffmpeg.txt
extern_libs/configure_options_libmpeg3.txt

Those configure_option files are read by the master .configure script

Installation:

./autogen.sh # includes the ./configure call
make
make install

GIMP is an acronym for GNU Image Manipulation Program. It is a freely distributed program for such tasks as photo retouching, image composition and image authoring.

Mpak is being designed from the ground up to be a kernel and architecture independent package manager for free operating systems.
Main features:
- a single statically linked executable: The package manager is responsible for installing all packages, including packages like glibc, which the whole system depends on. In the event that a critical package is damaged, we should be able to use the package manager to install a replacement for the package, so other system functionality can be repaired. To install a new operating system, a user will only need a boot CD (or an already running system) and a copy of the mpak executable
- dependency tracking: Mpak will be able to find and install all the dependencies for a package. Dependency cycles will be automatically handled via a bootstrapping mechanism.
- the package tree: Package metadata will be kept in a directory tree, organized by category. An installation of an mpak based distribution will have a "system" tree. There will be support for external trees provided by other vendors. Developers may provide package trees for their own projects.
- support for building from source and binary packages: Mpak will be able to use binary packages and build packages automatically from source.
- optional feature support: Many packages have optional build-time features. Mpak will have support for these. Following autoconfs lead, we will divide them into supported packages (e.g. --with-gnome) and internal features (e.g. --enable-mmx).
- kernel and architecture indepence: mpak will have features to simplify porting to different kernels. This way, we can have a unified distribution with support for many kernels (Linux, Hurd, BSD, Darwin, etc.), with nearly identical functionality across kernels.
- package binding support: mpak will be able to bind an installation of a package to another installed package. For example, suppose you have 2 versions of the linux kernel installed, 2.4.19 and 2.4.20. You want to install the alsa-drivers package for both of these kernels. Normally, you would only be able to install one copy of alsa-drivers, but mpak will let you bind the package to the linux kernel package, so that you can have one installation of alsa-drivers for each version of the linux kernel package you have installed.
- hard and soft dependencies: mpak will have support for hard and soft dependencies. Suppose package A has a hard dependency on package B. Then, when package B is upgraded, package A will need to be rebuilt. If package A had a soft dependency on package B, then A would not need to be rebuilt.

Software::Packager::Perl is used to package perl modules ready for installation and or distribution.

SYNOPSIS

use Software::Packager;
my $packager = new Software::Packager(perl);

It creates packages in the same format used to install all Perl modules.

FUNCTIONS

new()

This method creates and returns a new class object.

package()

This method overrides the base API and implements the required functionality to create Perl software packages.