Hi Peter! On Mon, 29 Oct 2007 20:49:53 +0100, Peter Van Eynde wrote:
Luca Capello wrote:
dpkg: warning - unable to delete old directory `/usr/lib/clisp/full': Directory not empty dpkg: warning - unable to delete old directory `/usr/lib/clisp': Directory not empty
Damn. I'll have to think about what I can do about this.
This problem occurs only during upgrade and not if someone remove or purge the package. This because clisp-1:2.41-1 has the following postrm (which is the same as clisp-1:2.42-3): ===== clisp_dir=/usr/lib/clisp mem=$clisp_dir/full/lispinit.mem lisp_run=$clisp_dir/full/lisp.run case "$1" in remove|failed-upgrade|abort-install|abort-upgrade|disappear) rm -f $mem $lisp_run || true ;; purge) rmdir -p --ignore-fail-on-non-empty $clisp_dir/full || true ;; upgrade) ;; *) echo "postrm called with unknown argument \`$1'" >&2 exit 0 ;; esac ===== Thus I think that upgrade should have something similar to 'remove plus purge' for /usr/lib/clisp/full (to correct the upgrade path). And maybe we should remove the $clisp_dir/full directly on 'remove' in the new versions, since I don't see the point in keeping the empty folder.
Is there any particular reason for clisp_2.42 to be installed in /usr/lib/clisp-2.42 instead of /usr/lib/clisp? Do we want to support installations of more than one clisp version?
clisp itself changed the location and it was easiest just to follow their lead.
Perfectly reasonable and fully ACK :-) Thx, bye, Gismo / Luca