Common Lisp in Debian Manual
Chapter 2 - Implementations

Note that in the following text, each occurence of implementation is to be replaced by the same name of the implementation in question.

2.1 Startup

Each Common Lisp implementation in Debian must provide the definitions of the Common Lisp Controller after startup. Their presence is required in non-interactive as well as interactive execution of the implementation. See Common Lisp Controller Setup, Section 1.2.

The implementation must load /etc/lisp-config.lisp.

2.2 Implementation Control Script

Implementations must provide a script located at /usr/lib/common-lisp/bin/implementation.sh that takes at least the following arguments:

install-clc

Installs the definitions of the Common Lisp Controller into the implementation. See Common Lisp Controller Setup, Section 1.2.

remove-clc

Restores the original state of the implementation without CLC definitions

The following actions are optional:

rebuild asdf-system-name

recompiles the library described by asdf-system-name.

remove destination-dir

deletes implementation-specific compiled object files of the library that is installed in destination-dir.

See Libraries, Chapter 3 for meanings of destination-dir and asdf-system-name. Installation of this script can be handled by the Debhelper for Common Lisp, see Common Lisp Debhelper, Chapter 4.

2.3 Maintainer Scripts

The following actions are required:

postinst

invokes /usr/sbin/register-common-lisp-implementation implementation when called with the configure argument and invokes /usr/sbin/unregister-common-lisp-implementation implementation when called with the abort-upgrade, abort-remove or abort-deconfigure argument.

prerm

invokes /usr/sbin/unregister-common-lisp-implementation implementation when called with the remove, upgrade or deconfigure argument.

The Common Lisp Debhelper (see Common Lisp Debhelper, Chapter 4) generates these scripts automatically.

Common Lisp in Debian Manual