etlegacy/Update-Installer
0
0
Fork 0
mirror of https://github.com/etlegacy/Update-Installer.git synced 2024-11-14 16:31:15 +00:00
Code Issues Projects Releases Packages Wiki Activity
Update-Installer/tools/README

22 lines
867 B
Text
Raw Normal View History

Add a script which creates the file_list.xml file and compressed packages for autoupdates from an installation directory and a package -> file map. * create-packages.rb takes an input directory containing all files as they are laid out in the installation directory of an application, a JSON file mapping files to packages and generates the file_list.xml file listing all files in the release along with the .zip packages containing those files. * Add single-package-map.json which is the simplest possible package map - putting all files in a single package. Per-project/build package maps can be written that separate files into different packages based on the component they belong to. This script replaces the autoupdate-setup tool written in C++ in the utilities/autoupdate-setup directory in the desktop source tree.
2011-08-25 17:50:03 +00:00
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,
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 15:09:11 +00:00
laid out as they are when installed and a JSON package config file,
this tool generates a set of packages for the release
Add a script which creates the file_list.xml file and compressed packages for autoupdates from an installation directory and a package -> file map. * create-packages.rb takes an input directory containing all files as they are laid out in the installation directory of an application, a JSON file mapping files to packages and generates the file_list.xml file listing all files in the release along with the .zip packages containing those files. * Add single-package-map.json which is the simplest possible package map - putting all files in a single package. Per-project/build package maps can be written that separate files into different packages based on the component they belong to. This script replaces the autoupdate-setup tool written in C++ in the utilities/autoupdate-setup directory in the desktop source tree.
2011-08-25 17:50:03 +00:00
and a file_list.xml listing all the files that make up the release.
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 15:09:11 +00:00
* config-template.json
Add a script which creates the file_list.xml file and compressed packages for autoupdates from an installation directory and a package -> file map. * create-packages.rb takes an input directory containing all files as they are laid out in the installation directory of an application, a JSON file mapping files to packages and generates the file_list.xml file listing all files in the release along with the .zip packages containing those files. * Add single-package-map.json which is the simplest possible package map - putting all files in a single package. Per-project/build package maps can be written that separate files into different packages based on the component they belong to. This script replaces the autoupdate-setup tool written in C++ in the utilities/autoupdate-setup directory in the desktop source tree.
2011-08-25 17:50:03 +00:00
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 15:09:11 +00:00
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
Add a script which creates the file_list.xml file and compressed packages for autoupdates from an installation directory and a package -> file map. * create-packages.rb takes an input directory containing all files as they are laid out in the installation directory of an application, a JSON file mapping files to packages and generates the file_list.xml file listing all files in the release along with the .zip packages containing those files. * Add single-package-map.json which is the simplest possible package map - putting all files in a single package. Per-project/build package maps can be written that separate files into different packages based on the component they belong to. This script replaces the autoupdate-setup tool written in C++ in the utilities/autoupdate-setup directory in the desktop source tree.
2011-08-25 17:50:03 +00:00
a release are placed in a single package. This means that the whole
package will need to be downloaded to install the update.
Reference in a new issue Copy permalink