Edit installation properties

Updated: September 12, 2023

The Edit Installation Properties dialog helps you control which packages will be added to your installations. You can change these properties at any time; you can also assign a different set of properties to each installation. For instance, you can assign one set of properties to an installation used for production purposes, and another set of properties to an installation used for experimental purposes.

A version of the Edit Installation Properties dialog appears automatically when you add an installation.

To access the dialog for an existing installation, follow these steps:

  1. Click the installation selector at the top-right of the main window, then select the desired installation.
  2. In the Advanced tab, click Edit Installation Properties.
  3. Set any of the properties in the following table, then click Apply to make sure they take effect.
Use this control: To:
Name Modify the name of the installation.
Variant

View the installation variant (for example, development seat or build server).

The installation variant is typically determined by the license key you selected when creating the installation.

Description Modify the description of the installation.
Update Policy Apply one of the following update policies to the installation:

Liberal

Install all updates during the initial installation. When subsequently installing a package, install the latest version of each dependent package.

Suppose, for example, that you are installing a filesystem update that requires libc, and that an update to libc is available. If you choose this policy, the QNX Software Center automatically installs the libc update.

Conservative

Install all updates during the initial installation. When subsequently installing a package, apply the following rules to dependent packages:
  • If a dependent package isn’t currently installed, install the latest version.
  • If a dependent package is already installed, use the existing version unless the package being added requires a newer version.

Let's return to above example, where you are installing a filesystem update and an update to libc is available. If you choose this policy, the QNX Software Center installs the update to libc only if the filesystem update specifically requires the libc update.

Ultraconservative

Don't install updates during the initial installation. When subsequently installing a package, install the earliest version of each dependent package that isn't already installed.

Suppose, for example, that you are installing a new package, and that it depends on other packages that aren't currently installed. If you choose this policy, the QNX Software Center chooses the oldest versions of those packages, even if later versions are available.

This option provides fine-grained control over your installation by letting you update individual packages to the versions you prefer.

If you choose this policy when adding an installation, the QNX Software Center installs original versions of all packages, without the latest updates.

Package Cache Location

Change the package cache location.

The package cache improves installation performance by storing copies of packages you have downloaded from the remote myQNX server. If you need to repair a package or install some packages more than once (for instance, to create another installation), the QNX Software Center uses the cached versions instead of downloading the packages again from the remote server.

The location defined here is used by all installations. Avoid changing it, unless you have a restriction on disk size in your home directory.

If you need to free up disk space, click the Clear Cache button. (You can also use File > Upkeep > Clear Package Download Cache). Note, however, that the cache will grow again if you download more packages.

The Package Cache Location and Clear Cache controls don't appear when you are adding an installation. They become available for the installation only after it has been added.

Automatically install patches

When installing a component, automatically install any patches or updates that the component requires.

If you uncheck this control, the installation of any component that requires patches or updates will fail, and you will need to add the patches or updates manually. You will, however, gain greater control over the contents of your installation.

This control doesn't appear when you are adding an installation. It becomes available for the installation only after the installation has been added.

Install debug symbols

View or install packages that contain only debug symbols, in addition to any other packages you are entitled to.

If you activate this option, the QNX Software Center also installs any associated debug symbols, when you subsequently install packages.

This checkbox turns on and remains activated if you select a package or group of packages in the Installed tab and then click the tab's Install Debug Symbols control. (Clicking the control tells the QNX Software Center to install the debug symbols for the selected package and for any updates or addons subsequently added to the installation.)

Install experimental packages

View or install experimental packages, in addition to any other packages you are entitled to.

You can install experimental packages only if this option is activated, even if you have the packages in hand and intend to install them offline.

This property automatically resets to on after the baseline installation to allow experimental packages in new installations. To install only stable packages, reset it after the baseline installation is complete.

If you want to disable the Install experimental packages flag, make sure that the current installation does not include any experimental packages which are already installed to avoid internal inconsistency and help with the update; otherwise, it will be internally inconsistent and you will not be able to update it.

Allow foreign host packages

Disable the host filter. You can install host packages from another host platform (i.e., Windows host packages on Linux).

If the host filter is disabled, the current host (installation host) type is considered as all type (meaning host type agnostic). If you choose this option, the QNX Software Center:
  • installs packages which have specific host requirements such as Windows-only packages on Linux host or the other way around.
  • does not automatically install any host toolchain for other hosts. You need to manually select the Install option after the original installation is finished.
Note: If this option is selected, shortcuts for Linux or Windows specifically are not created.
Target Architectures

Choose the architectures for which the QNX Software Center installs target packages.

The target architecture options let you hide packages for architectures you don't need to support. The options apply only to packages that are 100% target-specific, such as BSPs and reference images. Most other packages contain binaries for all architectures and, as such, aren't affected by these options.