Editing EPM Specification (section)

==The EPM Spec File==

The EPM Spec file contains a series of ":" separated keypairs, each on it's own line. Unless otherwise specified, ALL the fields detailed here are required. If a package wishes to add it's own configuration variables these should be added to the package's own configuration file and not the EPM spec.

The spec file should be called package_name ("package") in the spec file, e.g. (test_package.spec).

Example Spec file:
  package: test_package
  version: 0.0.1
  title: Test Package
  description: This is a simple test screen plugin
  creator: Dave Tarrant <davetaz@foo.bar.org>
  creator: Creator 2 <c2@foo.bar.org>
  configuration_file: Admin::TestScreen
  icon: icon.png
  license: GPLv2
  category: example
  category: input_output
  optional_key: key value
  

===package===
* A globally unique package identifier, used for management of the package versions, upgrades and local over rides.
* The main EPM repository will be files.eprints.org and this can be searched to find if your package_name exists. Alternatively files should tell you when you try and submit the package. 

===package_url (optional)===
* An official url for the package.

===version===
* A semantic version complient version number (major release . minor release . bugfix release)
* See http://semver.org/ for more details

===title===
* The title/name of the package. 
* A pretty string. 

===description===
* Description of the package.
* A pretty string. 

===creator===
* A creator listed as follows:
  Dave Tarrant <foo@bar.com>
* More than one creator can be specified by adding additional creator lines.

===icon===
* The icon file which should be within the root directory of the package

===category===
* The category of the plug-in, again multiple categories can be specified. 
* More can be found on these at http://bazaar.eprints.org (or via the store into which the package is being submitted). 


===configuration_file (not required)===
* A Screen or Config File in cfg/cfg.d.
If a cfg/cfg.d config file is listed (e.g. cfg/cfg.d/myscreen.pl), then the EPM Manager will re-direct the user to the built in editor for editing this config file. If a screen is specified (as per the example above) then the user will be re-directed to this screen when they press the configure button against the installed package.