We sometimes issue patches for LispWorks by email or download.
See Private patches below about location of your private patches.
Public patches are general patches made available to all LispWorks customers. These are typically released in bundles of multiple different patch files; each file has a number as its name. For example,
On receipt of a new patch bundle your system manager should update each local installation according to the installation instructions supplied with the patch bundle. This will add files to the patches subdirectory and increment the version number displayed by LispWorks.
You should consider saving a new image with the latest patches pre-loaded, as described in Saving and testing the configured image (Mac OS X), Saving and testing the configured image (Windows) or Saving and testing the configured image (Linux, x86/x64 Solaris or FreeBSD), or Saving and testing the configured image (other UNIX).
LispWorks patches are generally released in cumulative bundles. Occasionally Lisp Support may send you individual patch binaries named for example
my-patch to address a problem or implement a new feature in advance of bundled ('public') patch releases. Such patches have real names, rather than numbers, and must be loaded once they have been saved to disk. You will need to ensure that LispWorks will load your private patches on startup, after public patches have been loaded.
private-patches/ is the default location for private patches, and patch loading instructions sent to you will assume this location. Therefore, on receipt of a private patch
my-patch.ufasl, the simplest approach is to place it here. For example, on Mac OS X:
<install>/LispWorks 7.1 (32-bit)/Library/lib/7-1-0-0/private-patches/my-patch.xfasl
(LOAD-ONE-PRIVATE-PATCH "my-patch" :SYSTEM)
You may choose to save a reconfigured image with the new patch loaded - for details see the instructions in Saving and testing the configured image (Mac OS X), Saving and testing the configured image (Windows), Saving and testing the configured image (Linux, x86/x64 Solaris or FreeBSD), or Saving and testing the configured image (other UNIX). You can alternatively choose to load the patch file on startup. The option you choose will depend on how many people at your site will need access to the new patch, and how many will need access to an image without the patch loaded.
Note: On Windows, the correct way to install private patches is using the menu item
Help > Install Private Patches...
. Select the private patch file with the
button and edit the
private-patches/load.lisp in the lower pane to include the loading form supplied by Lisp Support immediately after the commented example there. Then click
, which will run a helper application that interacts with the Windows User Access Control mechanism to allow you to write the files into the protected Program Files folder.
LispWorks Release Notes and Installation Guide - 19 Oct 2017