LispWorks patches are generally released in cumulative bundles. Occasionally Lisp Support may send you individual patch binaries named for example
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 patch loading is controlled by the file:
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
, the simplest approach is to place it here. For example, on Mac OS X:
<install> /LispWorks 6.1/Library/lib/6-1-0-0/private-patches/my-patch.nfasl
<install> /lib/6-1-0-0/private-patches/my-patch.pfasl (for HP-PA)
<install> /lib/6-1-0-0/private-patches/my-patch.wfasl (for SPARC)
You will receive a Lisp form needed to load such a patch, such as
(LOAD-ONE-PRIVATE-PATCH "my-patch" :SYSTEM)
This form should be added to the
form in the file:
as in the commented example there.
loads this file, and hence all the private patches listed therein.
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.
On Windows Vista and Windows 7 you should save private patches and edit
while logged in as the user who will run LispWorks. If there are multiple LispWorks users, each user should do this.
LispWorks Release Notes and Installation Guide - 23 Dec 2011