Changes between Version 10 and Version 11 of UpdateVersions
- Timestamp:
- Mar 13, 2008, 10:41:32 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UpdateVersions
v10 v11 9 9 == Single-file application versions == #singlefile 10 10 11 File names must be of the form `NAME_VERSION_PLATFORM[ .ext]`, e.g.:11 File names must be of the form `NAME_VERSION_PLATFORM[_PLAN-CLASS][.ext]`, e.g.: 12 12 {{{ 13 boinc_3.17_i686-pc-linux-gnu14 13 astropulse_7.17_windows_intelx86.exe 15 14 }}} 16 15 * NAME is ignored; typically it is the app name. It may not containt underscores. 17 16 * VERSION is a string of the form N.M, where N and M are integers with M<100. This is converted to the single integer N*100 + M, which is used to specify application versions elsewhere in BOINC. M may have a leading zero, which is ignored. 18 17 * PLATFORM is the name of a platform in the database (if needed, [XaddTool add the platform to the DB]). 18 * PLAN-CLASS is an optional [AppPlan plan class] for the app version. 19 19 20 The file s on the example above would be on these paths:20 The file in the example above would have the path 21 21 {{{ 22 apps/boinc/boinc_3.17_i686-pc-linux-gnu23 22 apps/astropulse/astropulse_7.17_windows_intelx86.exe 24 23 }}} … … 26 25 == Multiple-file application versions == #multifile 27 26 28 Application 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.27 Application 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[_PLAN-CLASS][.ext]`) and put the files in that directory. 29 28 30 29 If 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>]). … … 61 60 (i.e., the application will be able to access the file 62 61 by passing the logical name to [BasicApi#Resolvingfilenames boinc_resolve_filename()]). 63 64 == Passing extra information about the app version ==65 66 If a file named '''plan_class''' is found, its contents will be used67 as the application's [AppPlan planning class].