NAME
Arepa::Builder - Arepa builder base "class"
SYNOPSIS
my $module = Arepa::Builder->ui_module;
Arepa::Builder->ui_module($new_ui_module);
Arepa::Builder->init($builder_name);
Arepa::Builder->compile_package_from_dsc($builder_name, $dsc_file);
Arepa::Builder->compile_package_from_dsc($builder_name, $dsc_file,
output_dir => 1);
Arepa::Builder->compile_package_from_repository($builder_name,
$dsc_file);
Arepa::Builder->compile_package_from_repository($builder_name,
$dsc_file,
output_dir => 1,
bin_nmu => 1);
my $log = Arepa::Builder->last_build_log;
Arepa::Builder->create($builder_dir, $mirror, $distribution);
DESCRIPTION
This module contains the interface for an Arepa builder. It should be the "subclass" for any builder module. Every Arepa builder type must have a module implementing this API. Arepa::BuilderFarm
, when manipulating the builders, will use the correct builder module according to the builder type (e.g. for type 'sbuild', Arepa::Builder::Sbuild
).
This module is never used directly, but through "subclasses" in Arepa::BuilderFarm
.
METHODS
- ui_module
- ui_module($ui_module)
-
Returns the UI module being used (by default,
Arepa::UI::Text
. If a parameter is passed, the UI module is changed to that, and the new value is returned. - init($builder_name)
-
Initialises the given
$builder_name
to be able to use it. This should be done once per machine boot (e.g. in an init script). - compile_package_from_dsc($builder_name, $dsc_file)
- compile_package_from_dsc($builder_name, $dsc_file, %opts)
-
Compiles the source package described by the given
$dsc_file
using the given$builder_name
. The resulting.deb
files are put in the current directory by default. Valid options areoutput_dir
andbin_nmu
(see compile_package_from_repository documentation). - compile_package_from_repository($builder_name, $name, $version)
- compile_package_from_repository($builder_name, $name, $version, %opts)
-
Compiles the source package with the given
$name
and$version
using the given$builder_name
. By default, the resulting.deb
files are put in the current directory. The only valid options areoutput_dir
(to specify the directory where the resulting.deb
files should end up in) andbin_nmu
(to specify if the compilation should be considered a binNMU). - last_build_log
-
Returns the log text of the last build.
- create($builder_dir, $mirror, $distribution);
-
Creates a new builder in the given directory
$builder_dir
, using the Debian mirror$mirror
and the distribution$distribution
.
SEE ALSO
Arepa::BuilderFarm
, Arepa::Config
.
AUTHOR
Esteban Manchado Velázquez <estebanm@opera.com>.
LICENSE AND COPYRIGHT
This code is offered under the Open Source BSD license.
Copyright (c) 2010, Opera Software. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Opera Software nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
DISCLAIMER OF WARRANTY
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
1 POD Error
The following errors were encountered while parsing the POD:
- Around line 235:
Non-ASCII character seen before =encoding in 'Velázquez'. Assuming UTF-8