Releasing application versions The update_versions script releases new application versions. It makes the needed database entries and copies files to the download directory.

To use:

Create an 'apps directory' under the project directory. Add an ", htmlspecialchars(""), " element to config.xml giving the path of the apps directory.
Create a subdirectory for each application, with the same name as the application. Put new application versions here. update_versions scans these directories for new application versions.

File names must be of the form NAME_VERSION_PLATFORM[.ext], e.g.:

boinc_3.17_i686-pc-linux-gnu.gz
astropulse_7.17_windows_intelx86.exe

The prefix name and extensions .gz, .exe, .sig are ignored.

Important notes:

Platform strings must match the names of platforms in the database. If needed, add the platform to the DB.
Your application must have the same major version number as your BOINC server software.

If a file of the form

EXEC_FILENAME.sig

is found, its contents will be used as a digital signature for the corresponding file. Recommended code-signing practices are described here.

Minimum core version

Application versions have a field min_core_version which, if nonzero, indicates the minimum core client version number to which the application version should be sent. Update_versions, by default, sets this to the largest core client version number in the database. You can disable this by editing update_versions, or by manually changing the app_version record.

Multiple-file application versions

Application versions can consist of multiple files. Follow the above procedure, but create a directory with the given name, and put the files in that directory. The executable file with the lexicographically first name will be treated as the main program.

Releasing core client versions

The same mechanism is used to release core client versions: Create a subdirectory 'boinc' in the apps directory, put new core client installer files there, and run update_versions. Core client versions will be visible to participants on your project's 'Download BOINC' web page.

NOTE: the files distributed in this way are installers, not executables. Instructions for creating installers are here.

NOTE: in the interests of consistency, we recommend that BOINC projects not distribute core client versions, but rather set the 'Download BOINC' link on their web page to point to the download page on the main BOINC site. Use this URL: http://setiweb.ssl.berkeley.edu/sah/download_boinc.php "; page_tail(); ?>