NAME

OTRS::OPM::Maker - Module/App to build and test OTRS packages

VERSION

version 0.03

DESCRIPTION

If you do OTRS package development, you need to be able to check your package: Are all files of the package included in the file list in the sopm file? Is the sopm file valid? And you need to create the OPM file. There is otrs.PackageManager.pl included in OTRS installations, but sometimes you might not have an OTRS installation on the machine where you want to build the package (e.g. when you build the package in a Jenkins (http://jenkins-ci.org) job).

OTRS::OPM::Maker provides opmbuild that is a small tool for several tasks. At the moment it supports:

• filetest

  Check if all files in the filelist exist on your disk and if all files on the disk are listed in the filelist

• somptest

  Checks if your .sopm file is valid

• dependencies

  List all CPAN- and OTRS- dependencies of your package

• build

  Create the OPM file

• devlink

  When you develop the package you might not want to build new version of your package and install it via the package manager. This command creates symlinks for each file of your package.

• devunlink

  Remove the symlinks created with devlink.

• index

  build an index file for an OPM repository.

Currently under development:

• remote_install

  Install the OPM file on any OTRS instance. That remote OTRS instance need an OTRS package installed (this is also under development)

• dbtest

  Check if the DatabaseInstall and DatabaseUninstall sections in your .sopm files are valid. And it checks for SQL keywords.

Ideas:

• devdb

  Do the DB changes needed for your package

AUTHOR

Renee Baecker <module@renee-baecker.de>

COPYRIGHT AND LICENSE

This software is Copyright (c) 2012 by Renee Baecker.

This is free software, licensed under:

  The Artistic License 2.0 (GPL Compatible)