Just a nit ... on my system, cmucl is flagged ~x86. Today, "emerge -puvlD world" told me an upgrade to dev-lisp/cmucl-19a-r1 was available (current is dev-lisp/cmucl-19a). But there was no changelog, and there isn't one in /usr/portage/dev-lisp/cmucl. Some users have way too much time on their hands.
Hi thanks for noting this, actually important, omission. I added a changelog to CVS, here it is for quick reference: *cmucl-19a (10 Feb 2004) 10 Feb 2005; Matthew Kennedy <mkennedy@gentoo.org> cmucl-19a-r1.ebuild: Support for Common Lisp Controller v4; Build CMUCL with CMUCL-CLX and CMUCL-GRAYSTREAM system defnitions by default -- this removes the ugly dependency some packages previously had on dev-lisp/cmucl-sources (which is now obsolete).
cmucl-sources is now obsolete? interesting ... how does cmucl bootstrap itself now? and does cmucl-sources still have a dependency on sbcl?
CMUCL still bootstraps itself with itself. Thats done in dev-lisp/cmucl which is a direct port from Peter Van Eynde's hard work in Debian. Traditionally Portage followed Debian's lead and supplied a cmucl-sources which contained ASDF-able cmucl-graystream, cmucl-clx etc and of course CMUCL's source (for "find-definition" lookups in SLIME/ILISP). I changed dev-lisp/cmucl-19a-r1 to install those ASDF by default and also install the CMUCL source by default (can be changed by using the "nosource" USE flag). For this reason, dev-lisp/cmucl-sources is no longer required. I don't quite know what you mean by "and does cmucl-sources still have a dependency on sbcl?". This was never the case. However whenever a dev-lisp/cl-* package required CMUCL to have graystream or CLX support, it depended on dev-lisp/cmucl-sources irrespective of whether you had CMUCL installed. This was confusing behaviour. Now packages no longer need dev-lisp/cmucl-sources, because dev-lisp/cmucl has it built in.
