Free rpm spec file software for linux

RPM::Util::Files is a Perl module to generate %files list in RPM Specfile.

SYNOPSIS

use RPM::Util::Files;

my $util = RPM::Util::Files->new({
build_root => /var/tmp/some-package-version-root,
docs_filters => [
sub {
my $entry = shift;

return $entry =~ /manuals/;
}
],
config_filters => [
sub {
my $entry = shift;

return $entry =~ /.conf$/;
}
],
});

$util->make_files;
print $util->to_string;

RPM::Make is a Perl module to cleanly generate an RPM.

SYNOPSIS

use RPM::Make;

# The "Manifest": list of files that will comprise the software package.
my @filelist=(tmproot/file1.txt,
tmproot/file2.txt,
tmproot/file3.txt,
tmproot/file4.txt);

my %doc; my %conf; my %confnoreplace; my %metadata;

# Define special handling of files.
$doc{tmproot/file1.txt}=1;
$conf{tmproot/file2.txt}=1;
$confnoreplace{tmproot/file3.txt}=1;

# Bare minimum metadata (descriptive data of the software package).
my $pathprefix=tmproot; # Location of files to be included in package.
my $tag=Test; # Default name of the software package.
my $version=0.1; # Version number.
my $release=1; # Release number (versions can have multiple releases).

# Highly descriptive metadata.
%metadata=(
vendor=>Excellence in Perl Laboratory,
summary=>Test Software Package,
name=>$tag,
copyrightname=>...,
group=>Utilities/System,
AutoReqProv=>no,
requires=>[(PreReq: setup,
PreReq: passwd,
PreReq: util-linux
)],
description=>This package is generated by RPM::Make. .
This implements the .$tag. software package,
pre=>echo "You are installing a package built by RPM::Make; .
RPM::Make is available at http://www.cpan.org/.",
);

# Temporary "sandbox" (this should not be /tmp because this is deleted!).
my $buildloc=TempBuildLoc;

# The "execute" subroutine coordinates all of the RPM building steps.
RPM::Make::execute($tag,$version,$release,$arch,$buildloc,$pathprefix,
@filelist,%doc,%conf,%confnoreplace,
%metadata);

# You can also build an RPM in more atomic steps; these three smaller
# steps are equivalent to the execute command.

# Step 1: Generate the rpm source location.
RPM::Make::rpmsrc($tag,$version,$release,$buildloc,$pathprefix,
@filelist,%doc,%conf,%confnoreplace,
%metadata);

# Step 2: Build the rpm and copy into the invoking directory.
RPM::Make::compilerpm($buildloc,$metadata{name},$version,
$release,$arch,
$currentdir,$invokingdir);

# Step 3: Clean the location used to gather and build the rpm.
RPM::Make::cleanbuildloc($buildloc);

Rpmorphan project finds "orphaned" packages on your system. It determines which packages have no other packages depending on their installation, and shows you a list of these packages.

It intends to be clone of deborphan debian tools for rpm packages.

RPM Wizard is an installation program for RPM packages. Using a wizard interface, it makes installing easy even for beginners. With features such as automatic dependency handling, it aims to become the most easy-to-use RPM installation program.
RPM Wizard is written in Python and uses the PyQt bindings for the Qt GUI toolkit. It is Open Source and available under the GNU General Public License.
Main features:
Ease of use
- RPM Wizard is designed to be as easy to use as possible. The program does not require any previous knowledge of how RPM works. When installed properly, the user can just click on an RPM file in the file manager and RPM Wizard starts automatically. The installation is supposed to go as smoothly as any Windows installation. If you think that something could be made more easy-to-use just drop me an email. No one knows better than the user.
Automatic dependency handling
- This is the new feature in RPM Wizard 0.6. A common problem when installing RPM packages is that the software is missing some dependencies, i.e some other software that is needed to get the program working. With most other RPM installers the user himself has to look for other RPM packages that satisfy the dependencies and install them first. RPM Wizard tries to do this automatically by searching a premade database of the content of the distribution CDs. If you are installing from a directory on your hard drive, it can also make use of the packages in that directory to satisfy the missing dependencies.
Install from a list of distribution packages NEW!
- If you have the RPM Wizard database module installed you can install packages by choosing the package name from a list. The list only includes packages that are newer than those installed. No longer will you have to search through all your distribution CD:s to find the package you are looking for.
Details dialog
- This dialog gives a lot of details for those interested without getting in the way for users that just want to get the installation through quickly. You can view the files of the package, the size, lists of provides and depends and more.
Shortcut on the desktop
- At the end of the wizard the user is given the option to put a shortcut on all users desktops (both KDE and Gnome).
Launch program
- This option starts the installed program as soon as the user clicks Finish.

rpm-analyzer is a graphical tool to help you analyze rpm dependencies. You can easily see what packages are required to install or remove a specific rpm.
RPM-Analyzer project may also help you to maintain a Red Hat-based distribution by providing hdlist and comps.xml analysis tools.
Main features:
This tool is based on a rpm database (hdlist).
After loading this database, youll be able to define a set of rpm, based on:
- the current system configuration
- predefined groups (from comps.xml)
- a user selection
This set of rpm:
- will automatically include the requiered dependencies.
- can be exported as an ASCII or HTML file.
You can easily view which packages are:
- requiered in order to add a specific rpm to your set.
- to be removed in order to remove a specific package from your set.
Enhancements:
- This release allows the users preferences to be automatically saved/restored.
- The packaging has been re-worked and the versioning changed.

easyRPM is a package management tool for RPM-based linux distributions. easyRPM helps you to explore packages that are installed on your computer, located on your hard disk, CD or in the web.

You can easily find packages by any criteria (name, size, feature, file, word in description). xml-based query language is supported. You may choose packages to install/remove and easyRPM will try to resolve all dependencies.

It will download required packages from the net. easyRPM can read header information from rpm files themselfs, yum xmls and hdlist files.

This tool is not yet full-featured, but already could be useful. If not, then give it a chance later.

Gem to rpm converter creates an RPM spec file from a Ruby gem. The project uses the gem metadata to fill out most of the information needed for building an RPM containing the gem.

Usage:

Run gem2rpm --help for options

At its simplest, download a gem (lets call that file GEM) and run

gem2rpm $GEM

This will print an rpm spec file based on the information contained in the gems spec file. In general, it is necessary to edit the generated spec file because the gem is missing some important information that is customarily provided in rpms, most notably the license and the changelog.

Rather than editing the generated specfile, edit the template from which the specfile is generated. This will make it easier to update the RPM when a new version of the Gem becomes available.

To support this process, it is recommended to first save the default template somewhere:

gem2rpm -T > rubygem-GEM.spec.template

Now, edit the template and then run gem2rpm to generate the spec file using the edited template:

gem2rpm -t rubygem-GEM.spec.template > rubygem-GEM.spec

With that, you can now build your RPM as ususal. When a new version of the gem becomes available, you should edit the saved template and rerun gem2rpm over it.

Template Details:

The template is a standard erb file; there are three main variables available in the template file:

format - The Gem::Format for the gem
spec - The Gem::Specification for the gem (the same as format.spec)

Conventions:

A typical source RPM for a gem should consist of three files: the gem file itself, the template for the spec file and the spec file. To ensure that the template will be included in the source RPM, it must be listed as one of the sources in the spec file.

The resulting rpms should follow the naming convention rubygem-$GEM where GEM is the name of the packaged gem. The default template also makes sure that the resulting package provides ruby($GEM), according to general packaging conventions for scripting languages