aboutsummaryrefslogtreecommitdiffstats
path: root/lib/sasl/test/installer.erl
diff options
context:
space:
mode:
authorSiri Hansen <[email protected]>2011-10-14 12:34:08 +0200
committerSiri Hansen <[email protected]>2011-11-17 16:47:28 +0100
commitd221b34133a8da8d62bdc57ebb724f86d7cd2fc0 (patch)
treee61faa27add14bf9c743e87ab4d5f3d00e428c32 /lib/sasl/test/installer.erl
parentbe04ed7beceeb4bcf5db7807e86df87e28c9f4b9 (diff)
downloadotp-d221b34133a8da8d62bdc57ebb724f86d7cd2fc0.tar.gz
otp-d221b34133a8da8d62bdc57ebb724f86d7cd2fc0.tar.bz2
otp-d221b34133a8da8d62bdc57ebb724f86d7cd2fc0.zip
Add restart_new_emulator instruction to kernel, stdlib and sasl appups
The appup files for kernel, stdlib and sasl did not contain any UpFromVsn and DownToVsn. This means that it was not possible to create a relup file with systool:make_relup if any of these applications had changed. This commit adds entries in the appup files for a maximum of two major releases back - all with only one upgrade instruction: restart_new_emulator. The point is to allow relups to be generated, but ensure that no soft upgrade is done for these three applications - i.e. they will always cause a restart of the emulator prior to all other upgrade instructions from other applications. Test cases (appup_test) are added to kernel_SUITE, stdlib_SUITE and sasl_SUITE. These all check that expected versions are matched in the appups, and illegal versions (older than two major releases, or in any other way illegal) do not match. The test is written in a general way where it is assumed that the version of these applications are stepped according the the rule that major releases step the second number, maintenance releases step the third number and patches step the fourth number.
Diffstat (limited to 'lib/sasl/test/installer.erl')
0 files changed, 0 insertions, 0 deletions