a)If I want to bundle the runtime with my application, how do I specify this in the application packager?
b)Even if I don't want to bundle the runtime I may want to specify it as a dependency, how do I do that?
c)How does the application launching mechanism and capability model work? Does:
1. The stub launcher starts the runtime in its own process, feeding it the script it needs to load
2. The stub launcher loads the runtime into the launcher process and feeds it the script it needs to load.
in other words, what do the capabilities I feed into ensymble actually do - are these going to be "obeyed" even if the runtime isn't signed with high enough capabilities? What if I feed in lesser capabilities than the runtime has - what will happen then.
d) I see you can display a text file on startup using textfile. Can you force text to be displayed on uninstall?
e) For autostart - does this use the startup list management API?
f) the profile is console or S60ui - presumably this defines what modules are specified as dependencies by default - if not, what does this *really* do?
g) ignore-missing-deps - I think what you are saying is that the packager will check your python script or folder and package all dependencies. If these can't be resolved this keyword will mean that the installer will still continue.
- is that correct
- are modules packaged whether or not they exist on the phone? what I'm getting at here is are there multiple copies potentially of modules on the phone?