
Documentation of the package description tags format. Have a look at the nasm
extension for examples and read ripclaws package howto for a more detailed
description.

 - Clifford

----


[D] [DOWN] [DOWNLOAD]

  Download a file. Only available for extension packages.


[P] [PRI] [PRIORITY]

  Package build order for 'Build-All'. No '[P]' means that the package will
  not be build by the 'Build-All' script.


[V] [VER] [VERSION]

  Package version and revision (example: '# [V] 2.3 19991204'). Only available
  for extension packages.


[I] [TITLE]

  a short description of the package. Can be given only once.


[T] [TEXT]

  a detailed package description.


[U] [URL]

  a URL related to the package.
  Format:  # [U] http://foo.bar/ Description of foo bar
  can be used more than once


[A] [AUTHOR]

  Format:  # [A] Clifford Wolf <clifford@clifford.at> {Core Maintainer}
  The <e-mail> and the {description} are both optional. Can be user more
  than once.


[M] [MAINTAINER]

  Same format as [A]


[L] [LICENSE]

  Format:  # [L] GPL
  I will add a list of possible values to Documentation/Developers/REGISTER

 
[E] [DEPS] [DEPENDENCIES]

  Format:  # [E] perl python gcc
  That means that at perl, python or gcc must be installed in order to
  build and run that package. There are no 'negative' dependecies saying
  'package foobar must not be installed'. Such a case can not exist as
  long as all packages are using the /opt/<package> tree. The [E] can
  be used more than once.


[S] [STATUS] [STABLE]

  Format:  # [S] Stable
  where 'Stable' can be one of a list of possible values. Suggestions for
  that value list are welcome. The [S] can only be used once per ext.
