Document doesn't match reality. Possible bug, but I don't know where.

Asked by David A. Cobb on 2017-08-07

/usr/share/doc/common-lisp-controller/DESIGN.txt specifies:
Common Lisp Implementations::

 Implementations should:
 - install a script /usr/lib/common-lisp/bin/<impl>.sh that has the following
   commands:
  /usr/lib/common-lisp/bin/<impl>.sh install-clc
   This should load /usr/share/common-lisp/source/common-lisp-controller/common-lisp-controller.lisp
   then call
(common-lisp-controller:init-common-lisp-controller-v4 "<name of implementation>")
   and then save the resulting image as default for the system for implementations that do
   not support a 'dump the current running image as new image' there is a v5 interface. See the
   ecl implementation for an example.
 - after install call "/usr/sbin/register-common-lisp-implementation <implementation>"
 - before removal call "/usr/sbin/unregister-common-lisp-implementation <implementation>"
 - should load /etc/lisp-config.lisp on startup.

However, I find
bash $ ll /usr/lib/common-lisp/bin/
total 0
drwxr-xr-x 1 root root 0 2012-10-28 21:29 ./
drwxr-xr-x 1 root root 6 2017-07-26 08:37 ../
superbiskit@BiskitHome:~

So, not one of the implementations (I have them all installed) follows this. I'm going to SWAG that the
"failure" is in the installer -- dh-lisp? Or CLC itself?
I think I know CLC is involved in installing lisp packages. I'm not wedded to the idea of using it as a lisp hacker;
but I want to avoid stepping all over the packaging policies or having them step all over me.

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu common-lisp-controller Edit question
Assignee:
No assignee Edit question
Last query:
2017-08-07
Last reply:
2017-08-23
Launchpad Janitor (janitor) said : #1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.