System Upgrade (SU) packages enable the device creators to overcome the restriction of using a Stub SIS file in the ROM for eclipsing.
A System Upgrade package is a package that has the RU flag set and is signed by a certificate that is chained to a root
certificate with the System Upgrade (SU) flag enabled.
This means that the upgrade package is as trusted as the base package.
The use of System Upgrade packages allows device creators to:
Solve system software problems at device build time.
Eclipse the Z drive files that are owned by other ROM Stub SIS files.
Note: To avoid possible problems for later upgrades of the ROM stub, it is important to track the stubs while preparing the eclipsing system upgrade packages.
Overwrite files owned by other packages when installing System Upgrade packages.
Note: This is not applicable for the SP system upgrade package.
Add, overwrite and eclipse files in any private folder on the Symbian device.
Notes:
Symbian device users can create a backup and restore eclipsing applications when the Symbian device is restored to factory state. Some applications that depend on the eclipsing packages do not work correctly if the eclipsing packages are not restored.
Any upgrades to System Upgrade package removes the previous package. Private directories are preserved.
When device creators uninstall a System Upgrade package, the private directories owned by the system upgrade are not deleted. This allows Symbian device users to return to the original software in the Z drive when needed.
The following
table shows whether each of the different upgrade types can be used
with the ROMUpgrade (RU) flag:
Upgrade type |
Supported |
Conditions |
SA |
Yes |
See Full Upgrades using System Upgrade packages (SA, RU) for details. |
PU |
Yes |
The |
SP |
Yes |
The For non-System
Upgrade packages, the |
PP |
No |
Not applicable. |
PA |
No |
Not applicable. |
For information about different upgrade types, see Upgrade Types.
Full Upgrades using System Upgrade packages (SA, RU)
To install
Full Upgrades (SA) using the System Upgrade package,
specify the ROMUpgrade (RU) flag in the header section
of the PKG file. For details, see Package-Header.
Notes:
The RU flag applies only to the SA package
it is in. It does not apply to any of the embedded packages inside
the SA.
After installing SA, RU type of upgrade, the SA files eclipse
the files in ROM. Any further upgrades remove the previously installed
SA package.
Installing SA, RU upgrade does not remove or replace the private directory
of the application.
The SA, RU upgrade can overwrite files previously created by
the ROM application in its private directory at runtime. Make sure
that the new versions of these files are compatible with the ROM application.
This is because if the upgrade is uninstalled, the files created by
the upgrade remain on the Symbian device.
The SA, RU upgrade removes any previously installed partial
upgrades (PU). The PU files must
be reinstalled.
This SA, RU upgrade does not remove previously installed patch
upgrades (SP).
The SIS files
that are installed using the software installer cannot be configured
to be non-removable. The SIS files that are preinstalled using InterpretSIS can be configured to be non-removable. The
following table provides conditions under which each of the System
Upgrade packages can install SIS files with the NR flag set.
SU upgrade type |
Supported |
Conditions |
SA |
Yes |
The Software Installer supports installation of non-removable |
PU |
Yes |
The Software Installer supports installation of |
SP |
Yes |
The Software Installer supports installation of non-removable SP packages when the base package is also non-removable and when SP is signed by a trusted certificate for eclipsing. This enables device creators to deliver non-removable augmentations to eclipsing packages. However, the software installer does not support the installation
of non-removable |
The Software Installer allows the NR flag
of an installed package to be modified using an SA or PU system upgrade package.