Changes between Version 4 and Version 5 of UpdateVersions


Ignore:
Timestamp:
Jul 16, 2007, 2:52:53 PM (17 years ago)
Author:
Nicolas
Comment:

Links and clarifications

Legend:

Unmodified
Added
Removed
Modified
  • UpdateVersions

    v4 v5  
    66 * If it doesn't already exist, create an directory 'apps' under the project directory, and add an <app_dir> element to config.xml giving the path of the apps directory.
    77 * Create a subdirectory for each application, with the short name of the application. Put new application files here (see below). `update_versions` scans these directories for new application versions.
    8  * From the project's root directory, run bin/update_versions.
     8 * From the project's root directory, run `./bin/update_versions`.
    99
    1010== Single-file application versions == #singlefile
     
    2424Application versions can consist of multiple files, one of which is the main program. To create a multiple-file application version, create a directory with the same name as the main program (of the form `NAME_VERSION_PLATFORM[.ext]`) and put the files in that directory.
    2525
    26 If your application includes executable files other than the main file, make sure that their protection flags include the user execute (u+x) bit.
     26If your application includes executable files other than the main file, make sure that their protection flags include the user execute (u+x) bit (`update_versions` will then set the `<executable/>` flag on its [XmlFormat#file_info <file_info>]).
    2727
    2828== Passing extra information about files == #extrainfo
     
    3232FILENAME.sig
    3333}}}
    34 is found, its contents will be used as a digital signature for the corresponding file. Recommended code-signing practices are described [CodeSigning here].
     34is found, its contents will be used as a digital signature for the corresponding file.See the [CodeSigning recommended code-signing practices].
    3535
    36 If a file of the form
     36If a file of the form 
    3737{{{
    3838FILENAME.file_ref_info
    3939}}}
    40 
    41 is found, its contents will be added to the <file_ref> element describing the file (you can use this for attributes like <copy_file>).
     40is found, its contents will be added to the [BoincFiles#file_ref <file_ref>] element describing the file (you can use this for attributes like [BoincFiles#file_ref <copy_file>]).
    4241
    4342If a file of the form
     
    4544LOGICAL_NAME=PHYSICAL_NAME
    4645}}}
    47 is found, the file will have the given logical and physical names (i.e., the application will be able to access the file by passing the logical name to boinc_resolve_filename()).
     46is found, the file will have the given logical and physical names (i.e., the application will be able to access the file by passing the logical name to [BasicApi#Resolvingfilenames boinc_resolve_filename()]).