The K Desktop Environment

Next Previous Table of Contents

3. Usage

3.1 Creation of a SPEC file from a KDevelop Project

  1. Press the IMPORT button and select a KDevelop project file.
  2. You will need to fill in the short project description, the revision number and the category that the application fits into. The URL line and the configure options are optional.
  3. Press the TEMPLATE button if you wish to use a template other than the default one.
  4. Press the SAVE button and save your spec file.

3.2 Creation of a SPEC file from scratch

Creating a spec file from scratch is a little more difficult because you will have to keep track of the version number and the application name. Because the source file is created from a combination of the application name and the version number you will have to make sure that these match the original source archive. To do this a good rule to follow is

{application name}-{version number}.tar.gz
Once this is accomplished you can fill in the other fields and then save the SPEC file as normal. This file will then need to be added to the tar.gz archive or put in the SPECS directory and the source put in the SOURCES directory.

3.3 Template File Specifications

The template specifications are as follows:

3.4 Special RPM usage

Once you have a SPEC file you can pass in local shell flags to the build process as follows:

% export LOCALFLAGS=--with-qt-dir=/usr/lib/qt-144
% rpm -ba somespec.spec
This will pass in any variables declared in LOCALFLAGS to the RPM. This is handy if your system has libraries in messed up places and you want others to be able to control where they are looking for the libraries.

Next Previous Table of Contents