How can I create debian packages using InstallBuilder?
| Author: BitRock Support Date: November 28, 2007 13:31 Tags: |
Installbuilder
Features Tips Native Packaging |
If you are using InstallBuilder Enterprise or InstallBuilder Professional, you can create Debian packages from your project file by selecting "DEB" as the build platform in the "Packaging" section of the builder application. In case you want to create the package from the command line, you can try the following:
/path/to/builder build /path/to/project.xml deb
InstallBuilder depends on dpkg to create Debian packages, so you will need to run the builder on a Linux distribution which provides Debian package support (such as Debian or Ubuntu).
Check below for the correspondence between DEB configuration fields and InstallBuilder ones:
DEB InstallBuilder
Version: <version>-<release>
Provides: <nativePackageName>
Maintainer: <vendor>
Description: <description>
The description on DEB packages holds a short single-line description plus a long description.
The short description is defined to be the first line inside the
The long description begins on the second line inside the <description>. Every line for the long description must be preceded by a single space character. By convenience the lines of the long description sh\ould not be too long.
Advanced Debian Package configuration
We have an advanced feature to generate custom Debian packages, implemented via a project property:<project> ... <debianCustomPackageDirectory>/path/to/some/folder</debianCustomPackageDirectory> ... </project> |
Inside that property, you specify a path to a folder containing all the scripts that go inside the typical DEBIAN folder when creating a .deb package:
control
preinst
postinst
prerm
postrm
Optionally, the control script may make use of several variables that are configurable from the project:
| Variable inside script | Project variables |
| ${bitrock_deb_version} | <version>-<release> |
| ${bitrock_deb_package} | <nativePackageName> |
| ${bitrock_deb_provides} | <nativePackageName> |
| ${bitrock_deb_maintainer} | <vendor> |
| ${bitrock_deb_description} | <description> |
In addition to that, we have:
| ${bitrock_deb_architecture} | Will resolve to "amd64" if we are on a Linux x64 system or "i386" if we are on a 32-bit Operating System |
| ${bitrock_deb_installedSize} | Will resolve to a value automatically calculated based on the sizes of the files packed inside the installer |
An example control script could be:
Essential: no
Architecture: ${bitrock_deb_architecture}
Description: ${bitrock_deb_description}
Provides: ${bitrock_deb_provides}
Package: ${bitrock_deb_package}
Section: misc
Maintainer: ${bitrock_deb_maintainer}
Priority: optional
Installed-Size: ${bitrock_deb_installedSize}
Version: ${bitrock_deb_version}
Depends : somepackage, someotherpackage
|