1 SASL Release Notes
This document describes the changes made to the SASL application.
1.1 SASL 2.1.9
Improvements and New Features
-
The re:grep/1 function now uses the 're' module instead of the deprecated 'regexp' module. There are new functions rb:filter/1 and rb:filter/2 for easier filtering of reports. (Thanks to Alvaro Videla.)
Own Id: OTP-8443
-
There is new function sasl_report:format_report/3 that works like the existing sasl_report:write_report/3 function except that it returns a formatted string. Note that there is currently no documentation for the sasl_report module. (Thanks to Jay Nelson.)
Own Id: OTP-8445
-
Cleanups suggested by tidier and modernization of types and specs.
Own Id: OTP-8455
1.2 SASL 2.1.8
Improvements and New Features
-
The documentation is now built with open source tools (xsltproc and fop) that exists on most platforms. One visible change is that the frames are removed.
Own Id: OTP-8201
1.3 SASL 2.1.7
Improvements and New Features
-
The Windows utility Erlsrv, run in interactive mode now accepts options for registering internal service name and description field of Windows registry database.
Own Id: OTP-8132
1.4 SASL 2.1.6
Fixed Bugs and Malfunctions
-
When using the SASL application configuration parameter masters the error tuple {error,{no_such_file,{Master,FileName}}} was sometimes returned even though the file FileName existed.
Own Id: OTP-7667
Improvements and New Features
-
Missing preloaded modules added
Own Id: OTP-7820
1.5 SASL 2.1.5.4
Improvements and New Features
-
A Dialyzer warning was eliminated
Own Id: OTP-7635
1.6 SASL 2.1.5.3
Improvements and New Features
-
Minor changes.
Own Id: OTP-7388
1.7 SASL 2.1.5.2
Improvements and New Features
-
Minor updates.
Own Id: OTP-6998
1.8 SASL 2.1.5.1
Improvements and New Features
-
Minor Makefile changes.
Own Id: OTP-6689
-
Obsolete guard tests (such as list()) have been replaced with the modern guard tests (such as is_list()).
Own Id: OTP-6725
1.9 SASL 2.1.5
Fixed Bugs and Malfunctions
-
Removed some dead code from erlsrv:get_service/2, release_handler:do_write_file/2, systools_relup:foreach_baserel_up/7 and systools_relup:foreach_baserel_dn/7.
Own Id: OTP-6499
1.10 SASL 2.1.4
Improvements and New Features
-
Added an option {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.
Also, when using 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.
As part of the work some minor bugs have been corrected:
-
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.
-
A documentation error for systools:make_tar/1,2: The .rel file is placed in the releases directory in the tar file, not releases/RelVsn.
Own Id: OTP-6226
-
1.11 SASL 2.1.3
Fixed Bugs and Malfunctions
-
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)
Own Id: OTP-6162
1.12 SASL 2.1.2
Fixed Bugs and Malfunctions
-
Fixed some minor bugs in release_handler found by Dialyzer.
Own Id: OTP-6039
1.13 SASL 2.1.1
Improvements and New Features
-
Added a number of functions to release_handler which makes it possible to test upgrade and downgrade of applications according to an .appup file "on the fly":
- upgrade_app/2
- upgrade_script/2
- downgrade_app/2,3
- downgrade_script/3
- eval_appup_script/4Own Id: OTP-5858
1.14 SASL 2.1
Improvements and New Features
-
A new option {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.
*** POTENTIAL INCOMPATIBILITY ***
Own Id: OTP-5761
1.15 SASL 2.0.1
Improvements and New Features
-
A bug that made it impossible to call rb:show(N) (N being an integer) twice without getting an error has been fixed.
Own Id: OTP-5287