How to integrate with the underlying package management system?

Comments

1 comment

  • Avatar
    wojciechka

    InstallBuilder provides two types of integration with native package system - building a native package (RPM/DEB) and normal installer that registers itself in the RPM/DEB registry.

    To enable RPM and DEB registration support add <registerWithPackageDatabase>1</registerWithPackageDatabase> to your installer project file. This will register your installation with the RPM and DEB database. From this point on, users will be able to query data about your application and its installed files using your distribution’s rpm-based tools as with any other existing rpm package. You will also be able to uninstall the application using your distribution’s rpm-based tools.

    Building a complete DEB/RPM package simply requires specifying rpm or deb as target platform - either from GUI or CLI.

    For example:

    $ path/to/builder build project.xml deb

    This will produce a native .deb package.

    Native packages do not offer full functionality of regular installers - they do not provide GUI and it is not possible to enable or disable components or change target directory. This is because the files are packaged in the rpm/deb file rather than installed by the installer. However, it is still possible to run actions - i.e. to perform finalization actions using the same InstallBuilder XML as in regular installer.

    Also please note that native packages have to be built on a Linux system that has the package command line tools installed - InstallBuilder uses those tools to generate the packages.

Please sign in to leave a comment.