Register Package
Previous Topic  Next Topic 

This action will attempt to register a package with the given package manager on the target system.  This action will almost always require root to be performed.  If the user is not already root, the action will attempt to execute the action as root which will prompt the user to enter their root password to install the package information.


Technical Detail

Currently-supported package systems are: DPKG and RPM.  The installer will attempt to build a dummy package on the target system using standard tools and then install it.  Because of the limitations of the build tools, this action does not register the files of your installer with the package database.


It does, however, register the uninstaller with the package system so that if the user attempts to remove the package through their system, it will call the uninstaller to do the actual file removal.


Note

InstallJammer will automatically add this package to be removed from the package database during uninstallation if the package is not being removed from the package manager itself.  This requires root access, and InstallJammer will prompt the user to execute the removal as root if they are not root when they run the uninstall.



Supported Platforms

Linux



Standard Properties 

See Standard Action Properties.



Advanced Properties


DPKG Changelog File

A file on the target system to use as the changelog file for the DPKG database.  If no file is specified, InstallJammer will create a dummy file to satisfy DPKG.  If the file does not have a .gz extension, InstallJammer will gzip the file as-per DPKG requirements.


DPKG Control Script

This is the script that will be used as the control script when DPKG builds our dummy package.  The default values and information will build a standard package based on information in your installer.


Note

Unless you are familiar with building DPKG packages, it is not recommended that you change any of the values in the Control Script.  This can lead to your package not building or not installing correctly.


DPKG Copyright File

A file on the target system to use as the copyright file for the DPKG database.  If no file is specified, InstallJammer will create a dummy file to satisfy DPKG.  If the file does not have a .gz extension, InstallJammer will gzip the file as-per DPKG requirements.


DPKG Debian Changelog File

A file on the target system to use as the Debian changelog file for the DPKG database.  If no file is specified, InstallJammer will create a dummy file to satisfy DPKG.  If the file does not have a .gz extension, InstallJammer will gzip the file as-per DPKG requirements.


DPKG Pre Install Script

A script to execute before installation in the DPKG database.  Since InstallJammer is doing most of the work here, you should probably leave this blank unless you know what you are doing.


DPKG Pre Uninstall Script

A script to execute before uninstallation in the DPKG database.  The default script is a standard script expected for all DPKG packages, and you should probably not change it unless you know what you are doing.


DPKG Post Install Script

A script to execute after installation in the DPKG database.  The default script is a standard script expected for all DPKG packages, and you should probably not change it unless you know what you are doing.


DPKG Post Uninstall Script

A script to execute after uninstallation in the DPKG database.  InstallJammer automatically populates this script with a script to call our uninstaller.  Since the DPKG database doesn't really know anything about the files in our installer or how to remove them, we want DPKG to remove its package and then call our uninstaller.


Since DPKG attempts to remove a previously-installed package before proceeding with a new install, this script checks to see if our removal is being run from another installer and exits if we are.


Package Name

The name of the package to use when storing this package to the database.  The rest of the information is stored in the different scripts that build our dummy packages.


Package Databases

Specifies which package database should be registered with on the target system.  Defaults to all, which means both RPM and DPKG if they exist on the system.


RPM Spec Script

The contents of this script are stored to a SPEC file to build our dummy RPM from.  The default values and information will build a standard package based on information in your installer.


Note

Unless you are familiar with building RPM packages, it is not recommended that you change any of the values in the Spec Script.  This can lead to your package not building or not installing correctly.