At this post http://answers.bitrock.com/questions/27/what-is-the-difference-between-rpm-packages-and-bitrock-installers You are referring to the following:
"There are scenarios where integration with the underlying package management system can be desirable. BitRock can provide support for generating RPM installers from a BitRock XML project file and integrating with the RPM database at installation time. Please email us if you are interested in these capabilities."
Yes, for my project we need this capability. Please send me the instructions as to how, using BitRock xml project file integrate with the RPM and DEB databases at install time?
asked 13 Sep '12, 13:39
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
Building a complete DEB/RPM package simply requires specifying
This will produce a native
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.
answered 14 Sep '12, 10:46