ext Mohammad Abu-Garbeyyeh <[email protected]> writes:
> Unfortunately, while this might be the right way, it caused me some problems
> with the enabler package, so to work around it, a terminal window is started
> from HAM (postinst) and then the postinst exits, the user then has to exit HAM
> and go back to the terminal window to continue installation.
Hmm, this sounds awkward. If I can, I would like to help you improve
this.
I haven't checked your enabler package yet, but off the top of my head,
what about this:
- You put a version 0 of mp-fremantle-community-pr into your repo that
has the exact same dependencies as the PR-1.3 mp-fremantle-generic-pr
meta package.
- You make a enabler package that configures the domains and keys and
everything, and also contains a little script that runs
apt-get install mp-fremantle-community-pr=0
This will just swap mp-fremantle-generic-pr out for
mp-fremantle-community-pr.
- The script has a launcher icon and you tell people to run it that
way. (Maybe this is the step that you want to avoid.)
- There is also a 'real' version of mp-fremantle-community-pr in the
repo, of course, and people can then immediately upgrade to it in
HAM.
This makes it so that the main upgrade runs inside HAM, which might be a
better user experience than running it inside a terminal.
I don't know if it actually works, but you can also put HAM into
red-pill mode and maybe enable the apt algorithms. Then you should be
able to see and install mp-fremantle-community-pr right inside HAM.
To put HAM into red-pill mode, you need to edit
~/.osso/hildon-application-manager.
Of course, you can also include a new version of HAM, or a completely
alternative installer UI, in mp-fremantle-community-pr version 0.
I guess I have overlooked something obvious, but maybe this gives you
some ideas...
_______________________________________________
maemo-developers mailing list
[email protected]
https://lists.maemo.org/mailman/listinfo/maemo-developers
