Version 7 (modified by davea, 7 years ago) (diff)


Creating application versions

The create new applications versions:

  • Create the directory structure described below to store applications files
  • From the project's root directory, run ./bin/update_versions.

Application directory hierarchy

Application versions are stored in a directory hierarchy under apps/ in the project root directory. The hierarchy has the following structure:

      ... other platforms
    ... other versions
  ... other apps

The version directories have names of the form PLATFORM or PLATFORM_PLANCLASS. The contents of a particular directory are:

  • application files
  • signature files (FILENAME.sig)
  • a "version description file", version.xml

The structure of version.xml is:

    [ <main_program/> ]
    [ <copy_file/> ]
    [ <logical_name>LNAME</logical_name> ]
    [ <url>URL0</url> ]
    [ <url>URLn</url> ]

File attributes include:

  • physical_name: the name of the file on disk.
  • main_program: designates the main program.
  • copy_file: the file is to be copied into the runtime directory on the client, rather than being linked to.
  • logical_name: if copy_file is present, then name of the file in the runtime directory.
  • url: URLs from which the file can be downloaded. Use this if you want to mirror your executables on separate servers. The executables must be present on the main server, at least while update_versions is run.

You only need to list files that have a main_program or copy_file attribute, or whose logical name is different from its physical name.

If the application has only one file (the main program), you don't need a version.xml file.

If your application includes executable files other than the main program, make sure that their user execute (u+x) flag is set (relevant for Unix and Mac versions).