diff -r 43e37759235e -r 51a74ef9ed63 Symbian3/SDK/Source/GUID-7A7254E3-A03A-5B38-B2B5-FFEEE70F5E93.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Symbian3/SDK/Source/GUID-7A7254E3-A03A-5B38-B2B5-FFEEE70F5E93.dita Wed Mar 31 11:11:55 2010 +0100 @@ -0,0 +1,39 @@ + + + + + +Embedded +SIS Files +

An embedded SIS file is a file that is placed in another SIS file. Embedded +SIS files are useful for packaging multiple components into a single SIS file. +These components can be removed independent of one another. For example, if +a SIS file needs to install an application and a library that is shared with +other installed applications, the shared library can be installed as an embedded +SIS file, so that when the application is uninstalled, the shared library +remains on the Symbian device if required.

+

Embedded SIS files are installed and removed along with the file that is +embedding the SIS file. However, an embedded SIS file cannot be removed if +another installed component has declared a dependency on +it. This depends on the security policy setting, RemoveOnlyWithLastDependent defined +in the installation policy file.

+ +

The Nested (embedding and the embedded) SIS files are processed as separate +installations. This means that the Embedding (outer) SIS file does not propagate +capabilities to the embedded (inner) SIS file. However, an Embedding (outer) +SIS file can be dependent on an embedded SIS file.

+

Note: If the installation of the embedded SIS fails, the entire +installation fails.

+

An embedded SIS file can be a partial upgrade (PU) or +patch upgrade (SP) package type. However, the base package +must have already been installed on the Symbian device. This implies that +if the base package and the upgrade are both embedded in the same SIS file, +the statement that installs the base package must occur in the source PKG +file before the statement that installs the upgrade or patch.

+
\ No newline at end of file