Packaging
---------

This directory holds the packaging metadata. The reason for the complexity is
that the metadata should be independent of the packaging format. Currently
this infrastructure supports RPM and DEP packages.

Each subpackage is described through a number of files holding the
metadata:

 <subpackage>.summary      - One line short summary
 <subpackage>.desc         - Longer description
 <subpackage>.filelist.in  - filelist
 <subpackage>.requires     - Requirements 
 <subpackage>.depends      - Ultimate requirements
 <subpackage>.recommends   - Beneficial requirements that are commonly installed
 <subpackage>.suggests     - Requirements that may be beneficial for some users
 <subpackage>.prefix       - Relocatable prefix

Currently only the "desc", "summary" and "filelist" files are required.

The mkfilelist takes 2 arguments:

  1. filelist
  2. Package format (rpm or deb)

and generates appropriate filelists


Specfile creation (RPM)
-----------------------

Specfile creation is done with the mkspec.sh which creates a spec file on
stdout upon invocation.

Control file creation (DEB)
---------------------------
Debian control is created from the toplevel debian directory using
mkcontrol.sh. Package prefix (eg. arc) is given as argument.

The changelog one is suggested to seed oneself, what may for for you
is an adaptation of the following:
cat build/changelog.in | sed -e 's/@PACKAGE@/nordugrid-arc0/' \
       -e "s/@DATER@/$(date -R)/" -e s/@VERSION@/0.8.trunk/ > debian/changelog
