Which leads me to the question: What's wrong with embedding?
What problem do you have that is *not* solved if one SIS embeds another?
I don't think that there is another solution, because otherwise a SIS would have to be able to contain more than one UID, and such an UID list is nowhere in sight, if you ask me.
Re: Is It Possible to Install the Two Applications With One Sis
I don't see why there is a problem flattening out the sis files into one sis file., You should be able to put all the files in one sis file.
There are specific use cases to do with capabiltiies that might be an issue with Symbian signed. For example if you have a self signed application and an embedded sis file that is Symbian signed then everything needs to be Symbian signed and the self signed files need to have their UID's changed to a protected range.
If there are specific issues that you see then you need to call them out here or on the Nokia boards
I guess the problem would occur with the package-header line, the one with # in front that gives the UID of the "component". The way I read the documentation, there can be more than one such line, but only because of different language versions of the *same* thing, not because the SIS file can (directly) contain more than one component.
Re: Is It Possible to Install the Two Applications With One Sis
The inbuilt assumption was that this was the same OS variant (UIQ or S60)
If remove components entirely from the sis file, then you can just merge all the files from the embedded pkg file into lines in the main pkg file.
Of course you would not have issues with duplicate vendor names, company names etc.
I had assumed the developer wanted to create a simple install due to the bugs with embedded sis files.
Obviously this model breaks down if the embedded sis file has higher capabiltiies or is sublicenced from a third party (where it is used in other applications such as PIP's)
Forum posts: 48
Yes....You can embed one sis into another while creating the second sis. Just add this line in your second PKG file.
@"First.SIS",(0x200049A5)
Here the UID have to be the the UID of your first APP.
Dushyant Gaur
Software Specialist,
Kodiak Networks,
No 401 Prestige Sigma, 4th Floor
3 Vittal Mallya Road
Bangalore - 560 001
India
Forum posts: 54
Hi dushyant_gaur,
thanks for giving the solution, i know this solution already,
i want it to be done other than this, i mean with out embedding the one sis into other
Thanks
Praveen
Forum posts: 1210
Which leads me to the question: What's wrong with embedding?
What problem do you have that is *not* solved if one SIS embeds another?
I don't think that there is another solution, because otherwise a SIS would have to be able to contain more than one UID, and such an UID list is nowhere in sight, if you ask me.
René Brunner
Forum posts: 140
I don't see why there is a problem flattening out the sis files into one sis file., You should be able to put all the files in one sis file.
There are specific use cases to do with capabiltiies that might be an issue with Symbian signed. For example if you have a self signed application and an embedded sis file that is Symbian signed then everything needs to be Symbian signed and the self signed files need to have their UID's changed to a protected range.
If there are specific issues that you see then you need to call them out here or on the Nokia boards
Paul Todd
Forum posts: 1210
I guess the problem would occur with the package-header line, the one with # in front that gives the UID of the "component". The way I read the documentation, there can be more than one such line, but only because of different language versions of the *same* thing, not because the SIS file can (directly) contain more than one component.
René Brunner
Forum posts: 140
The inbuilt assumption was that this was the same OS variant (UIQ or S60)
If remove components entirely from the sis file, then you can just merge all the files from the embedded pkg file into lines in the main pkg file.
Of course you would not have issues with duplicate vendor names, company names etc.
I had assumed the developer wanted to create a simple install due to the bugs with embedded sis files.
Obviously this model breaks down if the embedded sis file has higher capabiltiies or is sublicenced from a third party (where it is used in other applications such as PIP's)
Paul Todd