Free gem to rpm software for linux

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

gems is a project that shows a console session in several terminals in real time.

The gems system is a client/server application that allows you to show a single console session in different computers or terminals in real time.

It can also be used to transmit any other kind of data to more than one computer at the same time.

Commands to compile and install gems from sources

To compile:

$ make

To install (as root):

# make install

To uninstall (as root):

# make uninstall

Another quick & dirty Perl hack for RPM-based Linux distributions. Scans a directory of packages and finds out which ones are newer than the installed versions.

Its expecially useful if youre tracking the unstable branch of a distribution such as Fedora.

apt4rpm creates an apt, yum, or metadata repository from a random RPM directory.
Main features:
- Support for multiple distributions/versions/architectures in a single apt, yum or metadata repository.
- "Atomic" switching from an old apt repository to the newly created one.
- Analyzes the rpm packages in the rpm repository and creates a unified rpm package name. This mechanism uses caching to speed up the creation of subsequent created apt, yum or metadata repositories. The rpm name, version and architecture are stored seperately in the cache. This makes it possible to easily search for 1 particular rpm throughout the whole apt repository.
- Can create signed repositories.
- Can mirror download server directories after downloading the repositories will be created.
- If possible it will mark a package as a security update, and will put it in the "security" component of the repository.
- Provides an example sources.list file for the "file:", "ftp://" and "http://" protocols.
- The repositories are created with links from the rpm repository. The rpm repository can have any format. Rpms can be filtered with accept/reject rules.
- Creates seperated binary, source, delta and patch rpms components automatically.
- XML formatted config file
- The source-rpm apt components can be provided in a flat or noflat structure. Switching between those 2 can be performed without problem.
- A most recent rpm list can be created for each component.
- A contents list is created for the whole apt repository.

RubyGems is the premier ruby packaging system.
It provides:
- A standard format for destributing Ruby programs and libraries.
- An easy to use tool for managing the installation of gem packages.
- A gem server utility for serving gems from any machine where RubyGems is installed.
RubyGems Benefits
Using RubyGems, you can:
- download and install Ruby libraries easily
- not worry about libraries A and B depending on different versions of library C
- easily remove libraries you no longer use
- have power and control over your Ruby platform!
Main features:
- Easy Installation and removal of RubyGems packages and their dependents.
- Management and control of local packages
- Package dependency management
- Query, search and list local and remote packages
- Multiple version support for installed packages
- Web-based interface to view the documentation for your installed gems
- Easy to use interface for building gem packages
- Simple server for distributing your own gem packages

The RPM Package Manager also know as RPM is a powerful command line driven package management system capable of installing, uninstalling, verifying, querying, and updating computer software packages.
Each software package consists of an archive of files along with information about the package like its version, a description, and the like. There is also a related API ("Application Program Interface"), permitting advanced developers to bypass shelling out to a command line, and to manage such transactions from within a native coding language.
RPM is commonly found in the Linux computer operating system environment, but has been extended far beyond those initial confines.
A subset of the full RPM package feature-set is the baseline standard packaging format specified by the Linux Standard Base (which has as some of its goals to: "increase compatibility among Linux distributions and enable software applications to run on any compliant Linux system.")
Enhancements:
- Many fixes and enhancements were made.
- Most notably, this version merges efforts from several distributions into one commonly supported source tree.

Sigit is a customisable signature creator that can be run either as a daemon or as a normal foreground process.
It allows you to have a changing signature. If its configured correctly, it will also change the information displayed when someone fingers you.
It also supports multiple signature files for different newsgroups, and NFS-mounted $HOME shares.
Enhancements:
- his is a release toward making Sigit completely system independant, it introduces several checks against what is support on the target system.
- It also introduces some fixes which solves problems against gcc-4.
- Due to problems, with accessing an rpm based system, there wont be any rpm packages, neither src.rpm nor i386.rpm, in order to install it on an rpm based system you would need to get the tar.gz package, and use rpm-build in order to get the src and i386 packages.

Redline RPM Library is a pure Java library for manipulating RPM Package Manager packages. Currently the project supports reading and creating packages and has an included Ant task useful for integration with build systems. Support for package signatures will be added in a future release.
Enhancements:
- A patch has been merged that adds a Maven pom file, the directive for documentation files and directories, and user and group name attributes for files.