<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html xmlns:fn="http://www.w3.org/2005/02/xpath-functions">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" href="../../../../doc/otp_doc.css" type="text/css">
<title>Erlang -- SASL Release Notes</title>
</head>
<body bgcolor="white" text="#000000" link="#0000ff" vlink="#ff00ff" alink="#ff0000"><div id="container">
<script id="js" type="text/javascript" language="JavaScript" src="../../../../doc/js/flipmenu/flipmenu.js"></script><script id="js2" type="text/javascript" src="../../../../doc/js/erlresolvelinks.js"></script><script language="JavaScript" type="text/javascript">
<!--
function getWinHeight() {
var myHeight = 0;
if( typeof( window.innerHeight ) == 'number' ) {
//Non-IE
myHeight = window.innerHeight;
} else if( document.documentElement && ( document.documentElement.clientWidth ||
document.documentElement.clientHeight ) ) {
//IE 6+ in 'standards compliant mode'
myHeight = document.documentElement.clientHeight;
} else if( document.body && ( document.body.clientWidth || document.body.clientHeight ) ) {
//IE 4 compatible
myHeight = document.body.clientHeight;
}
return myHeight;
}
function setscrollpos() {
var objf=document.getElementById('loadscrollpos');
document.getElementById("leftnav").scrollTop = objf.offsetTop - getWinHeight()/2;
}
function addEvent(obj, evType, fn){
if (obj.addEventListener){
obj.addEventListener(evType, fn, true);
return true;
} else if (obj.attachEvent){
var r = obj.attachEvent("on"+evType, fn);
return r;
} else {
return false;
}
}
addEvent(window, 'load', setscrollpos);
//--></script><div id="leftnav"><div class="innertube">
<img alt="Erlang logo" src="../../../../doc/erlang-logo.png"><br><small><a href="users_guide.html">User's Guide</a><br><a href="index.html">Reference Manual</a><br><a href="release_notes.html">Release Notes</a><br><a href="../pdf/sasl-2.1.9.pdf">PDF</a><br><a href="../../../../doc/index.html">Top</a></small><p><strong>System Application Support Libraries (SASL)</strong><br><strong>Release Notes</strong><br><small>Version 2.1.9</small></p>
<br><a href="javascript:openAllFlips()">Expand All</a><br><a href="javascript:closeAllFlips()">Contract All</a><p><small><strong>Chapters</strong></small></p>
<ul class="flipMenu" imagepath="../../../../doc/js/flipmenu"><li id="loadscrollpos" title="SASL Release Notes" expanded="true">SASL Release Notes<ul>
<li><a href="notes.html">
Top of chapter
</a></li>
<li title="SASL 2.1.9"><a href="notes.html#id2257733">SASL 2.1.9</a></li>
<li title="SASL 2.1.8"><a href="notes.html#id2264277">SASL 2.1.8</a></li>
<li title="SASL 2.1.7"><a href="notes.html#id2264307">SASL 2.1.7</a></li>
<li title="SASL 2.1.6"><a href="notes.html#id2264340">SASL 2.1.6</a></li>
<li title="SASL 2.1.5.4"><a href="notes.html#id2264406">SASL 2.1.5.4</a></li>
<li title="SASL 2.1.5.3"><a href="notes.html#id2252834">SASL 2.1.5.3</a></li>
<li title="SASL 2.1.5.2"><a href="notes.html#id2252864">SASL 2.1.5.2</a></li>
<li title="SASL 2.1.5.1"><a href="notes.html#id2252895">SASL 2.1.5.1</a></li>
<li title="SASL 2.1.5"><a href="notes.html#id2252940">SASL 2.1.5</a></li>
<li title="SASL 2.1.4"><a href="notes.html#id2251912">SASL 2.1.4</a></li>
<li title="SASL 2.1.3"><a href="notes.html#id2261235">SASL 2.1.3</a></li>
<li title="SASL 2.1.2"><a href="notes.html#id2261282">SASL 2.1.2</a></li>
<li title="SASL 2.1.1"><a href="notes.html#id2260473">SASL 2.1.1</a></li>
<li title="SASL 2.1"><a href="notes.html#id2260546">SASL 2.1</a></li>
<li title="SASL 2.0.1"><a href="notes.html#id2260610">SASL 2.0.1</a></li>
</ul>
</li></ul>
</div></div>
<div id="content">
<div class="innertube">
<h1>1 SASL Release Notes</h1>
<p>This document describes the changes made to the SASL application.</p>
<h3><a name="id2257733">1.1
SASL 2.1.9</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
The <span class="code">re:grep/1</span> function now uses the '<span class="code">re</span>'
module instead of the deprecated '<span class="code">regexp</span>' module.
There are new functions <span class="code">rb:filter/1</span> and
<span class="code">rb:filter/2</span> for easier filtering of reports.
(Thanks to Alvaro Videla.)</p>
<p>
Own Id: OTP-8443</p>
</li>
<li>
<p>
There is new function <span class="code">sasl_report:format_report/3</span>
that works like the existing
<span class="code">sasl_report:write_report/3</span> function except that it
returns a formatted string. Note that there is currently
no documentation for the <span class="code">sasl_report</span> module.
(Thanks to Jay Nelson.)</p>
<p>
Own Id: OTP-8445</p>
</li>
<li>
<p>
Cleanups suggested by tidier and modernization of types
and specs.</p>
<p>
Own Id: OTP-8455</p>
</li>
</ul>
<h3><a name="id2264277">1.2
SASL 2.1.8</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
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.</p>
<p>
Own Id: OTP-8201</p>
</li>
</ul>
<h3><a name="id2264307">1.3
SASL 2.1.7</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
The Windows utility Erlsrv, run in interactive mode now
accepts options for registering internal service name and
description field of Windows registry database.</p>
<p>
Own Id: OTP-8132</p>
</li>
</ul>
<h3><a name="id2264340">1.4
SASL 2.1.6</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>When using the SASL application configuration
parameter <span class="code">masters</span> the error tuple
<span class="code">{error,{no_such_file,{Master,FileName}}}</span> was
sometimes returned even though the file <span class="code">FileName</span>
existed.</p>
<p>
Own Id: OTP-7667</p>
</li>
</ul>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
Missing preloaded modules added</p>
<p>
Own Id: OTP-7820</p>
</li>
</ul>
<h3><a name="id2264406">1.5
SASL 2.1.5.4</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
A Dialyzer warning was eliminated</p>
<p>
Own Id: OTP-7635</p>
</li>
</ul>
<h3><a name="id2252834">1.6
SASL 2.1.5.3</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
Minor changes.</p>
<p>
Own Id: OTP-7388</p>
</li>
</ul>
<h3><a name="id2252864">1.7
SASL 2.1.5.2</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
Minor updates.</p>
<p>
Own Id: OTP-6998</p>
</li>
</ul>
<h3><a name="id2252895">1.8
SASL 2.1.5.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>Minor Makefile changes.</p>
<p>Own Id: OTP-6689</p>
</li>
<li>
<p>Obsolete guard tests (such as list()) have been replaced
with the modern guard tests (such as is_list()).</p>
<p>Own Id: OTP-6725</p>
</li>
</ul>
<h3><a name="id2252940">1.9
SASL 2.1.5</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>Removed some dead code from <span class="code">erlsrv:get_service/2</span>,
<span class="code">release_handler:do_write_file/2</span>,
<span class="code">systools_relup:foreach_baserel_up/7</span> and
<span class="code">systools_relup:foreach_baserel_dn/7</span>.</p>
<p>Own Id: OTP-6499</p>
</li>
</ul>
<h3><a name="id2251912">1.10
SASL 2.1.4</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>Added an option <span class="code">{outdir,Dir}</span> to the functions in
<span class="code">systools</span>, making it possible to specify in which
directory a boot script, relup file or release package
file should be placed.</p>
<p>Also, when using <span class="code">systools:make_tar/2</span> to create a
release package file, the boot script, relup file and
<span class="code">sys.config</span> are now searched for also in the current
working directory and any directory specified by
the <span class="code">path</span> option, not only in the directory of
the <span class="code">.rel</span> file.</p>
<p>As part of the work some minor bugs have been corrected:</p>
<ul>
<li>
<p><span class="code">systools:make_script/1,2</span> now returns
<span class="code">error</span> if the <span class="code">.script</span> and/or <span class="code">.boot</span>
file could not be opened for writing, not <span class="code">ok</span>.</p>
</li>
<li>
<p><span class="code">systools:make_tar/1,2</span> can now handle a
<span class="code">RelName</span> argument which includes a path.
Previously this would cause the <span class="code">.rel</span> file to end
up in the wrong directory in the resulting tar file.</p>
</li>
<li>
<p>A documentation error for <span class="code">systools:make_tar/1,2</span>:
The <span class="code">.rel</span> file is placed in the <span class="code">releases</span>
directory in the tar file, not <span class="code">releases/RelVsn</span>.</p>
</li>
</ul>
<p>Own Id: OTP-6226</p>
</li>
</ul>
<h3><a name="id2261235">1.11
SASL 2.1.3</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p><span class="code">release_handler:upgrade_app/2</span> and
<span class="code">release_handler:downgrade_app/2,3</span> -- used for
testing application upgrade and downgrade according to
the <span class="code">.appup</span> file -- now update application
configuration parameters correctly. (Thanks to Serge
Aleynikov)</p>
<p>Own Id: OTP-6162</p>
</li>
</ul>
<h3><a name="id2261282">1.12
SASL 2.1.2</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>Fixed some minor bugs in <span class="code">release_handler</span> found by
Dialyzer.</p>
<p>Own Id: OTP-6039</p>
</li>
</ul>
<h3><a name="id2260473">1.13
SASL 2.1.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>Added a number of functions to <span class="code">release_handler</span> which
makes it possible to test upgrade and downgrade of
applications according to an <span class="code">.appup</span> file "on the
fly": <br>
- <span class="code">upgrade_app/2</span> <br>
- <span class="code">upgrade_script/2</span> <br>
- <span class="code">downgrade_app/2,3</span> <br>
- <span class="code">downgrade_script/3</span> <br>
- <span class="code">eval_appup_script/4</span></p>
<p>Own Id: OTP-5858</p>
</li>
</ul>
<h3><a name="id2260546">1.14
SASL 2.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>A new option <span class="code">{update_paths,Bool}</span> has been added
for <span class="code">release_handler:install_release/2</span>. It
indicates if all application code paths should be updated
(<span class="code">Bool==true</span>), or if only code paths for modified
applications should be updated (<span class="code">Bool==false</span>,
default).</p>
<p><span class="code">release_handler:set_unpacked/2</span> now returns an
error tuple if a specified application directory does not
exist.</p>
<p>*** POTENTIAL INCOMPATIBILITY ***</p>
<p>Own Id: OTP-5761</p>
</li>
</ul>
<h3><a name="id2260610">1.15
SASL 2.0.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>A bug that made it impossible to call <span class="code">rb:show(N)</span>
(<span class="code">N</span> being an integer) twice without getting an error
has been fixed.</p>
<p>Own Id: OTP-5287</p>
</li>
</ul>
</div>
<div class="footer">
<hr>
<p>Copyright © 1997-2010 Ericsson AB. All Rights Reserved.</p>
</div>
</div>
</div></body>
</html>
distrib
>
Fedora
>
13
>
i386
>
media
>
os
>
by-pkgid
>
f806c0f24240b25bde21a53f71766070
>
files
>
1283
