Automatic Software Updater: Difference between revisions
Jump to navigation
Jump to search
imported>Hendrik Brummermann No edit summary |
imported>Hendrik Brummermann No edit summary |
(No difference)
| |
Revision as of 20:20, 7 July 2011
Use cases
- U1. Updates of the production download-client (user)
- U2. Initial download and updates of the production webstart-client (user)
- U3. Running the client in a development environment (coder)
- U4. Adding resources to the production client by non coders (graphic and sound contributor)
- U6. Providing a production download-client without update (packagers for linux distributions)
- U7. Providing production download-client and webstart-client for a forked projects (third party developers)
Requirements
Internals
Creating update.properties
The updated files now need to be signed in a way that hides the signature from Java. This way we can use a long time key without risking evil-grade attacks.
The signatures are saved in update.properties and generated by
java -cp .:classes games.stendhal.tools.updateprop.UpdatePropUpdater /tmp/update-0.86.properties /tmp/out.txt 0.94 0.94.5 build/lib stendhal-0.94.5.jar stendhal-data-0.94.5.jar stendhal-data-diff-0.94-0.94.5.jar ...