DEBMAKER-EXTENSION(5) Manual Page

debmaker extensions extends the functionality of debmaker. Currently, extensions can do the following:

Users declare what extensions they’d like to use with the extensions variable in a PKGBUILD. Consider the following:

extensions=('strip' 'zipman')

Here the 'strip' and 'zipman' extensions are active.

All debmaker extensions are stored in a central location on the system, that being /usr/lib/debmaker on a standard installation. Each extension takes its own subdirectory in this directory (e.g. /usr/lib/debmaker/strip).

Each extension should have a script titled main.sh in its directory (i.e. /usr/lib/debmaker/strip/init.sh), inside of which there must be a function defined titled main. debmaker converts this function to be called debmaker-{extension_name} (where {extension_name} is the name of the extension, i.e. debmaker-strip), and the result is the public command, if any, that users can use to call the function inside of their PKGBUILDs. It is also used as the entrypoint for any hooks.

To capture the post-packaging build hook described at the top of this page, add the post_package=1 variable to the top of the init script, above any defined functions. The extension can then tell that debmaker itself called it as a post-packaging hook via the presence of the DEBMAKER_POST_PACKAGING variable, which will be set to the value of 1. The extension can also use this to only run itself when ran as a hook, by erroring out when the function is called without it being set.

debmaker will expose an extension’s main function with some extra environment variables:

Other variables may also set, but any present are for internal use and may be removed at any moment, so don’t rely on them being available.

Extensions may wish to expose more than one function to the end user - these may be defined inside of the main.sh script and will be loaded alongside the main function. Besides main, all functions in main.sh much start with {extension_name}- in order to be exposed to the user. These functions will also be prefixed with debmaker- when exposed to the user (i.e. strip-debug in main.sh would be exposed as debmaker-strip-debug).

Any other functions defined will not be available for use in the PKGBUILD. If for whatever reason you do need them, you can manually execute the extension’s main.sh script and run it via that manner. Note that you also shouldn’t source the extension’s main.sh (or any other files) when your extension executes though, as it may cause internal issues with conflicting function or variable names used by debmaker or PKGBUILDs.

debmaker(8) PKGBUILD(5)