clc is having problems. The design is getting Byzantine and in general much to complex to solve even seemingly obvious problems. The current design with build-daemon, cronjobs, spool directory etc. has to die. But what should replace it?
Kevin Rosenberg has a interesting idea: do not build for all users of the system anymore, just has a per-user cache of compiled packages in ~/.clc/
The major problems are that we would be deleting files in every user's homedirectory(!) and that we would not build all libraries on a routine basis, so bugs could go unnoticed for quite some time...
1 comment:
Deleting files in user directories is Bad. I am reasomably convinced of that.
That said, if you're upgrading to a newer library version there should be no need to: the dates on the source files will be newer and so asdf (I assume you're using asdf and overloading or :arounding the output-files method) will recompile them anyway.
(OK, this will lose if a user rebuilds a package after a new version is available in Debian but before the sysadmin has apt-getted it. OK. Maybe apt-get should touch all the source files after instllation, or something, if Debian doesn't mind the file dates changing from what they wree in the archive)
If you're upgrading the Lisp implementation, though, that's a bigger problem. There is a hack somewhere (for SBCL, at least) to make asdf recompile when the fasl is from an older version, but it's sufficient of a hack that I don't really want to put it in asdf itself.
-dan
Post a Comment