Releases and Patching
Jump to navigation
Jump to search
Releases
To build a release, check nant help for the current syntax of nant buildRelease.
The deliverables are:
- the tar.gz file which could be the base for manual installs, and for RPMS
- the tar.gz file is also used as a base for building the patches (see below)
- the standalone installer for Windows
- the remote client installer for Windows
Patches
- we use the bsdiff algorithm from http://www.daemonology.net/bsdiff/ for binary diffs and patching
- see more about the patchtool
patching the database
Standalone:
- standalone is always delivered with SQLite database
- we don't have patch installers yet. a full installer will update the program files, and add sql files for patching the database (setup\petra0300\standalone\patches). We cannot write to the user's directory, since the installer must be run as admin.
- on the next startup of OpenPetra Standalone by the user, csharp\ICT\Petra\Server\app\Main\ServerManager.cs EstablishDBConnection() will check for the database version, and UpdateSQLiteDatabase() will update the sqlite database
- this will also run "UPDATE s_system_defaults SET s_default_value_c = '{0}' WHERE s_default_code_c = 'CurrentDatabaseVersion';"