Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
titleExample

The complete URL for changelog.txt from the above example will be:

http://updateserver/smartgit/updates/changelog.txt.e6971f3e69c064e0468f13ae02a332b913f8e659

The file can be obtained from:

http://www.syntevo.com/updates/smartgit/changelog.txt.e6971f3e69c064e0468f13ae02a332b913f8e659

Details on control file HEADER fields

  • build specifies the SmartGit build number. It must match the autoupdate's <build>-element and the hard-coded build number in the SmartGit binaries. Hence, do never change this field.
  • minRequiredBuild specifies the minimum build number which the local installation must be of for a light-weight update (see Installation and Files). If the local build number is lower, an installation update will occur. Usually you will simply copy over control files as we have published them and only adjust the sourceRootUrl. In case you want to change the installation directory (see below) as part of the update, you have to set minRequiredBuild to the same value as build.
  • versionName and majorVersionName will only be used in the UI and should not be changed.
  • majorDate will be used to decide whether an upgrade to a new major version is supported by the license and should not be changed.
  • executable32bit and executable64bit specifies the binaries which will be launched after an installation update. Usually they should not be changed.
  • sourceRootUrl has been discussed already and must always be adjusted.
  • copyPatterns will be applied to all files in the old installation which were not known to be part of the old installation ("unknown files"), i.e. such files are not listed in the control-file of the old installation. Those unknown files which are matched by the pattern will be copied over to the new installation. For example, bin/smartgit.vmoptions is not part of the installation and hence will be copied over from old to new installation.
  • skipPatterns will also be applied to unknown files and directs SmartGit to ignore them when cleaning up the old installation. With regards to the cleanup, an unknown file may have been copied to the new installation, may have been skipped or may have not been handled in which case it will remain in the old installation. If the old installation is not empty after the cleanup, the SmartGit updater will warn about this fact and an -archive directory with the unhandled files will remain on disk.

Populating the updates "repository"

...