1. apparently, Matthew Kennedy has ported common-lisp-controller and some common-lisp implementations to gentoo and that's great ;-) thanks Matthew 2. but the idea behind common-lisp-controller is to compile packages for chosen installed implementations on debian where usually people install binaries. 3. on gentoo people usually install from sources so what's the point running some daemon from inetd which waits for (seldom) requests to compile installed lisp source? not to mention that daemon, instead of reporting problems to stderr like all ebuilds, tries to send some glib report using "/usr/bin/mail" (hmm i have it in "/bin/mail", but i don't wanna report separate bug about the application i want to see removed from gentoo). 4. i'm gonna uninstall common-lisp everything now and install cmucl from sources because i don't want to run inetd on every linux box i use to lisp. and i realy realy think common-lisp-controller should disappear. sorry :)
Hi Artem, (Please suggest an alternate approach if repopening this bug report (preferably with source code for an implementation).) I am not really keen on the common lisp controller either (especially its inetd approach), but it is a valid way to compile source for multiple compiler implementations, automatically and on demand (for whatever common lisp compilers the user has installed). The "glib" error message reported via mail is being improved. debug-daemon-problems.sh is being made gentoo specific and should handle the cases where the daemon is not running more gracefully. Perhaps in time we can change the controller to use some kind of setuid approach (eg. only members to a "clc-builder" group may recompile sources the controller manages). This is low priority work however. Matt
i guess i will reopen and accept this bug, as i've gone part way to modifying the clc-build-daemon into a standalone, setgid binary.
ok done :) Matt
