OTRS::OPM::Maker - Module/App to build and test OTRS packages
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).
opmbuild that is a small tool for several tasks.
At the moment it supports:
Check if all files in the filelist exist on your disk and if all files on the disk are listed in the filelist
Checks if your .sopm file is valid
List all CPAN- and OTRS- dependencies of your package
Create the OPM file
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.
Remove the symlinks created with
build an index file for an OPM repository.
Currently under development:
Install the OPM file on any OTRS instance. That remote OTRS instance need an OTRS package installed (this is also under development)
Check if the
DatabaseUninstall sections in your .sopm files are valid.
And it checks for SQL keywords.
Do the DB changes needed for your package
Renee Baecker <email@example.com>
This software is Copyright (c) 2012 by Renee Baecker.
This is free software, licensed under:
The Artistic License 2.0 (GPL Compatible)