Free deb packages software for linux

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.

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

Requires sudo and good configuration of sudo.

Package Wizard is a very useful tool that creates rpm, Debian and Slackware packages.
You need to install the Kommander (1.1) before:
http://www.kde-apps.org/content/show.php?content=12865
(it is the part of the kdewebdev3 package on SUSE),
and the checkinstall utility:
http://asic-linux.com.mx/~izto/checkinstall/download.php
The general rpm, Debian and Slackware package includes a service menu, so you can start it from the KDE context menu (section Actions).
TODO:
- Define alternetive for gcc and qt.
- Improve the check function before checkinstall.
Known bugs:
- After qmake, the file list display is not refreshed.
- The error messages are not redirected to the integrated konsole during ./configure.
- The error detection after compilation is not complete.
- Some problems maybe present for non-root users.
- Time stamp problems (during checkinstall) may be present on old rpm based systems.
Enhancements:
- The error detection after compilation is complete.
- Sound effects added.
- Simplified checkinstall/debhelper frontend.
- New buttons: Make clean, remove the directory debian/ from the source.

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.

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

Dpsyco is a automated system to distribute system configurations to several computers. It is written mainly for the Debian distribution but should be portable (without too much difficulties) to other distributions or Unixes as well.
It consists of a number of shell scripts to perform the desired actions. With it you can handle users, add ssh-public-keys, patch the system, update things using cfengine, install files (overriding other package files), and more.
Main features:
- Handle users.
- Handle groups.
- Handle ssh access.

debian-builder is a simple Perl script which is designed to rebuild a Debian package from its source. Some distributions such as Gentoo are focussed upon building packages from source code to give speed benefits, but that is not the aim of this program.
Ive been experimenting with a version of GCC which is patched to include stack smashing (buffer overflow) protection. One common approach to this problem is to use a modified compiler which will perform some kind of safety checking in potentially vulnerable source code - this usually involves applying a patch to the GCC compiler.
Usage:
Usage is fairly straight-forward and obvious simply run "debian-builder foo" to rebuild package foo.
If all goes well you will see some progress reports (more with --verbose) and a .deb file should eventually appear in /var/cache/debian-builder/deb.
The script will take care of installing all the packages which are required to build the named package, and then removing anything it installed afterwards.
Installation:
Simply download the tarball and run make install, alternatively you may download it from my apt-getable repository.
Enhancements:
- The handling of build dependencies is now much improved, allowing a greater number of Debian packages, including complex ones such as GNU Emacs and Mozilla Firefox.