/ 
PkgForge-Registry-1.3.0
River stage zero No dependents
/ PkgForge::App::Builder

NAME

PkgForge::App::Builder - Package Forge Registry App for managing build daemons

VERSION

This documentation refers to PkgForge::App::Builder version 1.3.0

SYNOPSIS

pkgforge builder list

pkgforge builder add --name foo_f13 --plat f13 --arch i386

pkgforge builder del --name foo_f13

DESCRIPTION

This is a Package Forge application for managing the registered build daemons. It makes it easy to list, add and delete build daemons for particular target platforms.

It is not expected that this class will be used directly, it is designed to provide a command for the pkgforge(1) command-line tool.

ATTRIBUTES

This class has the following attributes which are mapped into command-line options when used via the pkgforge application.

configfile

This is the name of the file from which the Package Forge Registry configuration should be loaded. If not specified then the default, /etc/pkgforge/registry.yml will be used.

name

The unique name of the build daemon.

platform

The name of the target platform supported by the build daemon. For example, f13 or sl5.

architecture

The architecture of the target platform supported by the build daemon. For example, i386 or x86_64.

SUBROUTINES/METHODS

The class has the following methods which are mapped into sub-commands without the leading action_ for the pkgforge application.

action_list

Ths action lists all the registered build daemons. It does not use any of the attributes (or command-line options).

action_add

This action adds a new build daemon. You must specify a unique name for the daemon, the name of the platform and the architecture via the relevant attributes (or command-line options). Note that it is not possible to add a build daemon for a platform/architecture combination which has not already been registered and activated.

action_delete

This action deletes the entry for a build daemon. You must specify the name of the build daemon via the relevant attribute (or command-line option).

It is not generally a good idea to remove a build daemon entry once it has been used to carry out build jobs as the database keeps a log of what has done and you will lose history.

CONFIGURATION AND ENVIRONMENT

The Package Forge Registry configuration file can be specified via the configfile attribute (or command-line option). If not specified then the default, /etc/pkgforge/registry.yml will be used.

DEPENDENCIES

This module is powered by Moose and uses MooseX::App::Cmd and MooseX::Types.

SEE ALSO

PkgForge, PkgForge::Registry, pkgforge(1)

PLATFORMS

This is the list of platforms on which we have tested this software. We expect this software to work on any Unix-like platform which is supported by Perl.

ScientificLinux5, Fedora13

BUGS AND LIMITATIONS

Please report any bugs or problems (or praise!) to bugs@lcfg.org, feedback and patches are also always very welcome.

AUTHOR

Stephen Quinney <squinney@inf.ed.ac.uk>

LICENSE AND COPYRIGHT

Copyright (C) 2010 University of Edinburgh. All rights reserved.

This library is free software; you can redistribute it and/or modify it under the terms of the GPL, version 2 or later.