-
Notifications
You must be signed in to change notification settings - Fork 21
DSL of Debian Builder
Gerry Weißbach edited this page Aug 13, 2019
·
1 revision
The deb
task is responsible for building Debian packages using Setup Builder.
The following options are available to the deb
task:
deb {
// Sets the installation root of the software application
// defaults to /usr/share/{setupBuilder.application}
installationRoot = "/usr/share/my-application"
// defines a file that will be stored in /etc/default/{serviceName}
// ususally contains default information for the service starter.
defaultServiceFile = "default-service.txt"
// a script that will be included into the default service starter script
additionalServiceScript = "<script>"
// true (default), if the default service (aka the first service defined)
// should start after installation
startDefaultService = false
// The user the services will be executed with, defaults to root
daemonUser = "root"
// Architecture of the installer, defaults to "all"
architecture = "all"
// List of recommended software components to install along the application
recommends = "java | python3"
// List of software components the application depends on
depends = "java | python3"
// the section is alike the category, defaults to "Application/Productivity"
section = "Application/Productivity"
// sets the homepage of the vendor for this application
homepage = "https://www.inetsoftware.de"
}
The following additional options are available to the deb
task:
deb {
// a priority of the application, defaults to "optional"
priority = "optional"
// optional, size to expect when the package is installed.
installSize = "10"
// optional, uses lintian to check the package definition if true
checkPackage = false
// optional, lintian options. will only be used if deb.checkPackage == true
lintianOptions = ""
// e-mail address of the maintainer of this package.
maintainerEmail = "[email protected]"
// String of changes in this package
changes = ""
}
To allow even more customization during installation you can use several installation script entry points. Please have a look at the specifc documentation.