Free build deb packages software for linux

Debian Package Tools FE application is the first part of the Debian Package Tools FE based on python-qt3.
Debian Package builder FE is a frontend for dh-make, dpkg-dev, debhelper. It is a tool to learn to build packages for Debian based systems without any knowlegde concerning the above command line applications. Debian Package builder cannot fix build dependences and repair non-standard sources. It is only a graphical frontend.
This debug release is only for testing on your system. Debian Package Tools FE is not intended for non Debian based systems. If it works, you are lucky, but if it does not, I will not restrict the ability of the application for the shake of a restricted system. (It will not work on SUSE, because Qscintilla package does not contain the full version Qscintilla.)
Debian Package Builder FE was not tested on Ubuntu. Theoretically, it could work from Breezy, but the package dependences may not allow you to install it. In this case, I will include an Ubuntu version, just test it.
This is a debug release. In case of any error, you can test it by the command (from running from the console):
dpkg-tools-fe full_path_to_the_tarball/tarball_name.tar.gz or tar.bz2,
or without argument:
dpkg-tools-fe.
Enhancements:
- Threading improvements to increase process stability
- A solution for a python-qt bug in Debian 4.0.
- Postinst script improvements. Prerm script to clean-up.

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

Requires sudo and good configuration of sudo.

Linux::Distribution::Packages Perl module contains a list all packages on various Linux distributions.

SYNOPSIS

use Linux::Distribution::Packages qw(distribution_packages distribution_write);

$linux = new Linux::Distribution::Packages({format => csv, output_file => packages.csv});
$linux->distribution_write();

# Or you can (re)set the options when you write.
$linux->distribution_write({format => xml, output_file => packages.xml});

# If you want to reload the package data
$linux->distribution_packages();

This is a simple module that uses Linux::Distribution to guess the linux distribution and then uses the correct commands to list all the packages on the system and then output them in one of three formats: native, csv, and xml.
Distributions currently working: debian, ubuntu, fedora, redhat, suse, gentoo, slackware, redflag.

The module inherits from Linux::Distribution, so can also use its calls.

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.

PkgBuilder is a simple system for automatically creating software packages (in formats such as RPM, tgz, or Deb) from source code.

It is meant to be similar to the "ports" system found in BSD, but for Linux.

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.

AcuLaser C900 CUPS backend provides a LINUX CUPS package (incl. PPD-file) for the EPSON AcuLaser C900.
It is built around the avasys pipsplus driver. The project supports i386 and 32-bit compatible x86_64 LINUX systems (deb/rpm/tgz/gentoo/slack)
There are positive feedbacks for:
- SuSE
- Mandriva
- Slackware
- Red Hat
- Fedora Core
- Debian, Ubuntu
- Gentoo
The included installer will:
- Check for missing packages
- download and install the mandatory epkowa packages automatically
- provide a dummy lpr-package to resolve dependencies
- account for the different Ditros (BSD - System V - Gentoo) and configure the run-levels accordingly
- give suggestions for appropriate URIs for the printer installation
- call the distribution specific CUPS tools (YaST2, printerdrake, kprinter, gnome-cups-config)
Main features:
- Bundling of pages (large documents sometimes "hang")
- generic multiple local printer support
- URI handling for proper interface (usblp) allocation
- installation of XML files for plain foomatic support
- better hotplugging behavior
- networking (IPP, SMB) support through a local pseudo-interface
Enhancements:
- The regular print mode will be selected with every reboot or runlevel change.