etlegacy/Update-Installer
0
0
Fork 0
mirror of https://github.com/etlegacy/Update-Installer.git synced 2024-11-29 23:22:04 +00:00
Code Issues Projects Releases Packages Wiki Activity
Update-Installer/tools
History
Robert Knight ddb52aa244 Change the package-map JSON file into a general config file which also specifies the name of the updater and path to the main binary. 
The generated file_list.xml needs to specify the path
 of the main binary and the name of the updater binary
 to download.  Change the format of the JSON config file to
 allow these paths to be specified there.

 * Update create-packages.rb to add the <is-main-binary> attribute
   to the appropriate entry in file_list.xml

 * Modify the sample config file

 * Improve documentation in create-packages.rb
2011-08-27 16:09:11 +01:00
..
config-template.json Change the package-map JSON file into a general config file which also specifies the name of the updater and path to the main binary. 2011-08-27 16:09:11 +01:00
create-packages.rb Change the package-map JSON file into a general config file which also specifies the name of the updater and path to the main binary. 2011-08-27 16:09:11 +01:00
README Change the package-map JSON file into a general config file which also specifies the name of the updater and path to the main binary. 2011-08-27 16:09:11 +01:00

README 

This directory contains a set of tools for preparing auto-updates.

 * create-packages.rb

	Given a directory containing the set of files that make up a release,
	laid out as they are when installed and a JSON package config file,
	this tool generates a set of packages for the release
	and a file_list.xml listing all the files that make up the release.

 * config-template.json

    This is a template for the config file that specifies:

	- How to partition the files that make up an installed application
	  into packages.
	- The path of the main binary to run after the update completes
	- The name of the updater binary to download as part of the update

    This is the simplest possible package configuration, where all files for
	a release are placed in a single package.  This means that the whole
	package will need to be downloaded to install the update.