Descriptive configuration data for lilac packaging
The prefix of build command to be used. E.g. extra-x86_64, multilib or archlinuxcn-x86_64.
Name of function to be used as the pre_build function.
Name of function to be used as the post_build function.
Name of function to be used as the post_build_always function.
Body of the pre_build function. lilac2.api functions are available.
Body of the post_build function. lilac2.api functions are available.
Body of the post_build_always function. lilac2.api functions are available.
Time limit in hours. The build will be aborted if it doesn't finish in time. Default is one hour.
Packages in the repo that are direct dependencies of the current package.
Package (directory) name
Package base (directory) as key and package name as value
Packages in the repo that are in makedepends or checkdepends of the current package.
Package (directory) name
Package base (directory) as key and package name as value
Configure how nvchecker should check for updates / rebuilds? The first should check for updates and others for rebuilds.
nvchecker configuration section
nvchecker source name
use an alias for nvchecker configuration section
alias name
Build this package if the configured packages are built in the same batch. Note that the packages should also be added to "repo_depends".
on_build configuration
pkgbase to build on
a regex to transform pkgbase's version. This requires database support to be enabled for lilac.
a replacement string to transform pkgbase's version to. This requires database support to be enabled for lilac.
List of maintainers for receiving email notifications
GitHub username with a public email address
GitHub username and an email address in the form "Name <user@host>". The GitHub public email does not matter.
Whether to stage the package in a "staging" subdirectory
Whether the package should be built by lilac or not