Archived:Creating a dependency to embedded SIS files

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata

---

Compatibility

Platform(s): S60 3rd Edition, S60 3rd Edition, FP1

---

Article

Created: User:Technical writer 2 (25 Apr 2007)

Last edited: hamishwillee (14 Jun 2012)

Overview

When using embedded SIS packages, the (parent) SIS package should also declare a dependency to the embedded SIS, if it is required to run the application.

Description

Embedding a SIS file does not automatically create a dependency to it. Without the dependency, the system will not warn the user when trying to remove the embedded component via the Application Manager.
With the dependency, the user is shown the following warning:
"Removal may stop other applications from working. Continue anyway?"

Solution

If the embedded component is required to run the application, add a dependency  to it in the application .pkg file:
; Embedded sis
@"depend.sis",(0x23456789)
; Dependency and required version
(0x23456789), 1, 30, 0, {"RequiredComponentName"}