This document describes the changes made to the SASL application.
{outdir,Dir} to the functions in
systools, making it possible to specify in which
directory a boot script, relup file or release package
file should be placed.systools:make_tar/2 to create a
release package file, the boot script, relup file and
sys.config are now searched for also in the current
working directory and any directory specified by
the path option, not only in the directory of
the .rel file.systools:make_script/1,2 now returns
error if the .script and/or .boot
file could not be opened for writing, not ok.systools:make_tar/1,2 can now handle a
RelName argument which includes a path.
Previously this would cause the .rel file to end
up in the wrong directory in the resulting tar file.systools:make_tar/1,2:
The .rel file is placed in the releases
directory in the tar file, not releases/RelVsn.
release_handler:upgrade_app/2 and
release_handler:downgrade_app/2,3 -- used for
testing application upgrade and downgrade according to
the .appup file -- now update application
configuration parameters correctly. (Thanks to Serge
Aleynikov)
release_handler found by
Dialyzer.
release_handler which
makes it possible to test upgrade and downgrade of
applications according to an .appup file "on the
fly":upgrade_app/2upgrade_script/2downgrade_app/2,3downgrade_script/3eval_appup_script/4
{update_paths,Bool} has been added
for release_handler:install_release/2. It
indicates if all application code paths should be updated
(Bool==true), or if only code paths for modified
applications should be updated (Bool==false,
default).release_handler:set_unpacked/2 now returns an
error tuple if a specified application directory does not
exist.
rb:show(N)
(N being an integer) twice without getting an error
has been fixed.