diff -r ebc84c812384 -r 46218c8b8afa Symbian3/PDK/Source/GUID-474A9F80-2B3E-5D11-8D2E-95E217BEB84A.dita --- a/Symbian3/PDK/Source/GUID-474A9F80-2B3E-5D11-8D2E-95E217BEB84A.dita Thu Mar 11 15:24:26 2010 +0000 +++ b/Symbian3/PDK/Source/GUID-474A9F80-2B3E-5D11-8D2E-95E217BEB84A.dita Thu Mar 11 18:02:22 2010 +0000 @@ -1,53 +1,53 @@ - - - - - -Preinstalled -Package Upgrades -

Packages that are preinstalled using InterpretSIS must follow certain rules -while upgrading, as explained in the following sections:

-
Standard upgrade rules

InterpretSIS supports the -following upgrade types:

- -

* The base SA and associated upgrades are removed ** The base SA -is removed prior to the installation of the SA upgrade.

InterpretSIS -returns an error if the rules are violated during an upgrade. It supports -variants of file names and usage of wildcards for Stub SIS files.

-
Non-removable package upgrade rules

The following -table summarises the rules that apply when performing patch upgrade, partial -upgrade or replacement of non-removable packages installed using InterpretSIS. -The general rule is that a removable package cannot be made non-removable, -and a non-removable package cannot be made removable.

- -

* If the partial upgrade modifies files in the SP, -the PU(NR) is modified when the SP is removed.

** -The original PA is removed, including the private directory, -before upgrading.

Notes:

    -
  • NR upgrades are performed to the same drive as the -original package.

  • -
  • NR upgrades or patches delivered on preinstalled media -cards are rejected as invalid. Any invalid upgrade generates a KErrInvalidUpgrade error.

  • -
  • Back-up and restore is not functional for preinstalled SIS files that -are in the system drive.

  • -
  • Preinstalled SIS files that are in the system drive can be uninstalled -if DeletePreinstalledFilesOnUninstall is set in swipolicy.ini file. -For details see, Secure -Software Install Reference.

  • -
-
-InterpretSIS - -Preinstalling -Packages -Upgrade Types - -Eclipsing - + + + + + +Preinstalled +Package Upgrades +

Packages that are preinstalled using InterpretSIS must follow certain rules +while upgrading, as explained in the following sections:

+
Standard upgrade rules

InterpretSIS supports the +following upgrade types:

+ +

* The base SA and associated upgrades are removed ** The base SA +is removed prior to the installation of the SA upgrade.

InterpretSIS +returns an error if the rules are violated during an upgrade. It supports +variants of file names and usage of wildcards for Stub SIS files.

+
Non-removable package upgrade rules

The following +table summarises the rules that apply when performing patch upgrade, partial +upgrade or replacement of non-removable packages installed using InterpretSIS. +The general rule is that a removable package cannot be made non-removable, +and a non-removable package cannot be made removable.

+ +

* If the partial upgrade modifies files in the SP, +the PU(NR) is modified when the SP is removed.

** +The original PA is removed, including the private directory, +before upgrading.

Notes:

    +
  • NR upgrades are performed to the same drive as the +original package.

  • +
  • NR upgrades or patches delivered on preinstalled media +cards are rejected as invalid. Any invalid upgrade generates a KErrInvalidUpgrade error.

  • +
  • Back-up and restore is not functional for preinstalled SIS files that +are in the system drive.

  • +
  • Preinstalled SIS files that are in the system drive can be uninstalled +if DeletePreinstalledFilesOnUninstall is set in swipolicy.ini file. +For details see, Secure +Software Install Reference.

  • +
+
+InterpretSIS + +Preinstalling +Packages +Upgrade Types + +Eclipsing +
\ No newline at end of file