Free software package software for linux

Software::Packager::Rpm is a suite of Perl modules providing a common interface for
the creation of platform specific software installation packagers.

add_item()
my %object_data = (
SOURCE => /source/file1,
TYPE => file,
KIND => doc,
DESTINATION => /usr/local/file1,
USER => joe,
GROUP => staff,
MODE => 0750,
);
$packager->add_item(%object_data);

This method overrides the add_item method in Software::Packager. It adds the ability to add extra features used by RPM for each object in the package.

For more details see the documentation in: Software::Packager Software::Packager::Object::Rpm

program_name()
$packager->program_name(SoftwarePackager);
my $program_name = $packager->program_name();

This method is used to set the name of the program that the package is installing. This may in should be the same as the package name but that is not required. It must not contain spaces or a dash "-" and must be all on one line.

version()
$packager->version(1.2.3.4.5.6);
my $version = $packager->version();

This method sets the version for the package to the passed value. The version passed cannot contain a dash "-" or spaces and must be on one line.

release()

This method sets the release version for the package. The release is the number of times the package has been recreated. If the release is not set then a default of 1 is used. It cannot contain spaces, a dash or new lines.

copyright()

This method sets the copyright type for the package. This should be the name of the copyright

source()

This method sets the source location for the package. This should be the URL for the source package used to create this package.

architecture()
$packager->architecture("sparc");
my $arch = $packager->architecture();

This method sets the architecture for the package to the passed value. If no argument is passed then the current architecture is returned. This is the output "from uname -p"

package_name()
my $name = $packager->package_name();

This method returns the name of the package that will be created.

short_description()

$packager->short_description("This is a short description.");
my $description = $packager->short_description();

The short description is just that a short description of the program. It must be all on one line.

description()
$packager->description("This is the description.");
my $description = $packager->description();

The description method sets the package description to the passed value. If no arguments are passed the package description is returned.

The discription can be of any length. It will be formatted by RPM in the following way:
If a line starts with a space it will be printed verbatim.

A blank line signifies a new paragraph.

All other lines will be assumed to be part of a paragraph and will be formatted by RPM.

package()

This method creates the package and returns true if it is successful else it returns undef

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.

Fedora Package Menu is a service menu for easy installation of downloaded RPMs.

Requires sudo and good configuration of sudo.

slackget10::Package this class is the internal representation of a package for slack-get 1.0.

SYNOPSIS

This module is used to represent a package for slack-get

use slackget10::Package;

my $package = slackget10::Package->new(package-1.0.0-noarch-1);
$package->setValue(description,"This is a test of the slackget10::Package object");
$package->fill_object_from_package_name();

CONSTRUCTOR

new

The constructor take two parameters : a package name, and an id (the namespace of the package like slackware or linuxpackages)

my $package = new slackget10::Package (aaa_base-10.0.0-noarch-1,slackware);

The constructor automatically call the fill_object_from_package_name() method.

You also can pass some extra arguments like that :

my $package = new slackget10::Package (aaa_base-10.0.0-noarch-1, package-object-version => 1.0.0);

The constructor return undef if the id is not defined.

Membership project allows you to keep accurate and up to date membership records online.
Features membership import, to bring your membership in from another software package. Also features membership export feature for creating mailings.
Search your membership and store information and pictues about each member.
Enhancements:
- This release fixes a few minor bugs found in the authentication module.

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.

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.