|Allegro CL version 9.0|
Unrevised from 8.2 to 9.0.
Arguments: &key documentation-only destination-directory except-patches force host list patches platform verbose version (keep-old-patches t) proxy proxy-basic-authorization
This function contacts the Franz Inc. website and downloads the patches appropriate for your platform (computer type) and version of Allegro CL. In order to work, the computer running Allegro CL must be able to make an FTP connection to the internet. If the connection is not made for any reason, update-allegro signals an error.
On Windows using the IDE, the Download Patches dialog can be used to call this function.
Calling this function with no arguments will download and install all patches.
If you have AllegroCache or AllegroGraph installed, update-allegro will tell you if there are newer versions available (but it does not itself download these newer versions).
Unless the force argument is true, a patch file is not downloaded if the size and CRC (checksum) of an existing local file with the same name and location is the same as the remote file (but this does not cause an error or prevent downloading of other files).
Fasl file (destined for the update/ and various other directories), shared library (UNIX), and Dynamically Linked Library (DLL) patches are all handled by sys:update-allegro. On Windows, because "in use" files cannot be replaced, you will be asked to reboot your computer to finish the update process. Without rebooting, you will not see the patched DLL.
The keyword arguments to sys:update-allegro are as follows:
t. If true, old patch files are renamed to end in "bak" (or if a "bak" file is present, a numbered "bak" file -- "bak2", "bak3", etc.) Thus, if a new, modified code/streams.fasl is downloaded, the older one becomes streams.faslbak and if a new p2a002.001 is downloaded, the old one becomes p2a002.001bak. (This makes it easier to back out of a patch, particularly a patched fasl file in the code/ directory.) If the value of this argument is
nil, the old file is overwritten.
We recommend that if possible you do not specify this argument and instead call sys:update-allegro on the platform of interest. (However, there might be cases, such as where the desired platform is not connected to the internet, where using this argument is necessary.)
nil. Allows using an http proxy. See Note on using proxies below the argument descriptions.
nil, can be in one of two formats. The first allowable format is a cons of two strings: the username and the password, like this:
:proxy-basic-authorization (cons "username" "password")
The second allowable format for this argument is a string of the form "username:password". See Note on using proxies below the argument descriptions.
Users that surf through an http proxy (usually as a security measure
on sites with firewalls) can specify the proxy name and port number
using the proxy keyword argument, and, if
necessary, a username and password using the
argument. Suppose the proxy is
www.foo.com and it
uses port 8000, then such users would specify the sys:update-allegro form like this
(specifying other arguments as desired, of course):
(sys:update-allegro :proxy "www.foo.com:8000")
If a username and a password is also, needed, they can be specified like this (replacing "username" and "password" with the actual strings and also specifying other arguments as desired):
(sys:update-allegro :proxy "www.foo.com:8000" :proxy-basic-authorization (cons "username" "password") )
or, using the second allowable format for proxy-basic-authorization:
(sys:update-allegro :proxy "www.foo.com:8000" :proxy-basic-authorization (cons "username:password") )
Without proxy specified, sys:update-allegro will try and contact
www.franz.com directly. In the case where users are
using a proxy, that would not work. The failure symptom would be that
just hang and finally time out.
To download all available patches for your platform and version, do:
If you want all patches except update/p2a001.001, then do this:
(sys:update-allegro :except-patches '("update/p2a001.001"))
If you want a list of patches that would be downloaded but do not want to download anything, then do this:
(sys:update-allegro :list t)
It is important that you follow the instructions given to you by sys:update-allegro. It may ask you to rebuild your images or, on Windows only, to reboot your machine. If you do not follow the instructions, the update procedure will not be complete.
On Windows, when a reboot is necessary, sys:update-allegro displays a dialog asking you if you want to reboot immediately, and performs the reboot if you answer `yes'. Even if you do not reboot immediately, you should reboot before using Allegro CL further.
Patches are described in section Patches of introduction.htm. The sections after that one also contain information about patches.
Copyright (c) 1998-2012, Franz Inc. Oakland, CA., USA. All rights reserved.
Documentation for Allegro CL version 9.0. This page was not revised from the 8.2 page.
|Allegro CL version 9.0|
Unrevised from 8.2 to 9.0.