etlegacy/Update-Installer
0
0
Fork 0
mirror of https://github.com/etlegacy/Update-Installer.git synced 2024-11-14 00:10:57 +00:00
Code Issues Projects Releases Packages Wiki Activity
Update-Installer/tools
History
Robert Knight b39c71638a Add required --platform and --version arguments to the package creation script and allow the updater binary to be specified with a -u option 
These specify the target version for the update and the platform and are embedded
in the <targetVersion> and <platform> elements of the generated file_list.xml file

Ordinarily the script will use the updater binary from the input files directory which
matches the path of the updater binary specified in the package config file.

However it may sometimes be necessary to use a different binary, which can be done
via a -u option.
2011-09-01 12:47:10 +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 Add required --platform and --version arguments to the package creation script and allow the updater binary to be specified with a -u option 2011-09-01 12:47:10 +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.