Configuration

Structure

- conf
  - pfm
    - roles              = PEAR_PackageFileManager2 'roles' option: default are
                           $roles = array(
                                'h' => 'src',
                                'c' => 'src',
                                'm4' => 'src',
                                'w32' => 'src',
                                'dll' => 'ext',
                                'php' => 'php',
                                'html' => 'doc',
                                '*' => 'data',
                                 );
    - dir_roles          = PEAR_PackageFileManager2 'dir_roles' option: default are
                           $dir_roles' = array(
                                'docs' => 'doc',
                                'examples' => 'doc',
                                'tests' => 'test',
                                 );
    - changelogoldtonew  = PEAR_PackageFileManager2 'changelogoldtonew' option: default is TRUE
    - simpleoutput       = PEAR_PackageFileManager2 'simpleoutput' option: default is FALSE
    - exportcompatiblev1 = FALSE
    - baseinstalldir     = '/'
    - outputdirectory    = PEAR_PackageFileManager2 'outputdirectory' option: default is FALSE
    - package_type       = array('php','extsrc','extbin');
    - stability          = array('snapshot','devel','alpha','beta','stable');
    - maintainer_roles   = array('lead','developer','contributor','helper');
    - filelistgenerator  = array('File', 'Cvs', 'Svn', 'Perforce');
  - gui
    - actions            = array('display' => 'ActionDisplay', 'process' => 'ActionProcess', 'dump' => false);

This configuration file is divided into 2 parts:

• 'pfm' that will set options related to PEAR_PackageFileManager2 options
• 'gui' that allow to change behavior of PEAR_PackageFileManager2 web frontend

PFM part

• outputdirectory: the path in which to place the generated package.xml by default, this is ignored, and the package.xml is created in the packagedirectory.
• roles: this is an array mapping file extension to install role. This specifies default behavior that can be overridden by the exceptions option and dir_roles option. use addRole() to add a new role to the pre-existing array.
• dir_roles: this is an array mapping directory name to install role. All files in a directory whose name matches the directory will be given the install role specified. Single files can be excluded from this using the exceptions option. The directory should be a relative path from the baseinstalldir, or "/" for the baseinstalldir.
• changelogoldtonew: True if the ChangeLog should list from oldest entry to newest. Set to false if you would like new entries first.
• simpleoutput: True if the package.xml should be human-readable.
• exportcompatiblev1: This option can be also change on Preview tab, before commit changes. True if you want fully compatible package.xml version 1.0, false if you want only the package.xml version 2.0
• baseinstalldir: the base directory to install this package in. For package PEAR_PackageFileManager, this is "PEAR", for package PEAR, this is "/".
• package_type: this is the list of package type supported by PEAR_PackageFileManager2 web frontend.
• stability: this is the list of stability API and release options found on Release tab. You may be restrict or extends options, depending of PEAR future.
• maintainer_roles: this is the list of maintainer roles found on Maintainers tab. You may be restrict or extends options, depending of PEAR future.
• filelistgenerator: this is the plugin list which can be used on Replacements tab. There are actually 4 generator plugins, that may be restrict or extends, depending of PEAR future.

GUI part

There are only 3 actions that may be change to allow new behavior of web frontend:

• display to change render (see QuickForm Renderer).
• process to change result of abort, commit and reset buttons.
• dump to add a tool to debug application easily.