clc v6 and debconf6
May. 18th, 2006 03:56 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
pvaneyndI released common-lisp-controller 6 which has one major change: if you now compile a lisp file not under clc (or slime) control then the resulting fasl file will end up in /var/cache/common-lisp///local/ so that on upgrade of the implementation all cached fasl files will be removed. To give an example compiling /home/luser/cl-world-control/mind-beam.lisp will result (on sbcl) in /var/cache/common-lisp/1001/sbcl/home/luser/cl-world-control/mind-beam.fasl
The only problem with this is that is you remove the source-tree the cached fasl files will not get removed, but I guess people do upgrades with regularity (for sbcl every month or so) and sysadmins know that anything in /var/cache may be nuked at any moment.
For debconf6 I'm blogging about it on my non-debian and lisp blog (so that my non-debian friends read it) and uploading pictures to a special debconf6 flickr set.
The only problem with this is that is you remove the source-tree the cached fasl files will not get removed, but I guess people do upgrades with regularity (for sbcl every month or so) and sysadmins know that anything in /var/cache may be nuked at any moment.
For debconf6 I'm blogging about it on my non-debian and lisp blog (so that my non-debian friends read it) and uploading pictures to a special debconf6 flickr set.
