Bug 29983 - dev-lisp/cmucl-bin-18e-r1 doesn't insall a lisp.core file
Bug#: 29983 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: CLOSED Severity: normal Priority: P2
Resolution: NEEDINFO Assigned To: mkennedy@gentoo.org Reported By: geoff@gentoo.org
Component: Ebuilds
URL: 
Summary: dev-lisp/cmucl-bin-18e-r1 doesn't insall a lisp.core file
Keywords:  
Status Whiteboard: 
Opened: 2003-09-30 04:24 0000
Description:   Opened: 2003-09-30 04:24 0000 
The new r1 ebuild for cmucl-bin-18e doesn't symlink the dist lisp core to
/usr/lib/cmucl/lisp.core - this results in /usr/bin/lisp failing to run if you
don't specify a -core. It also means that the
register-common-lisp-implementation cmucl line in the postinst won't be able to
run (so no asdf if you subsequently do symlink a lisp.core until you register
with clc again).

Fix: change the src_install section to add a symlink from
/usr/lib/cmucl/lib/lisp-dist.core to /usr/lib/cmucl/lisp.core

------- Comment #1 From Geoff Cant 2003-09-30 04:26:19 0000 ------- 
Created an attachment (id=18527) [details]
patches r1 ebuild to symlink a lisp.core during installation

------- Comment #2 From Matthew Kennedy (RETIRED) 2003-10-01 20:20:11 0000 ------- 
Hi Geoff, I think that the lisp.core is made by loading the clc into
lisp-dist.core
and then dumping. this should be done in the pkg_postinst with
register-common-lisp-implementation.
 The only explantion I can think of at the moment, is that inetd was not
running at the time you emerged cmucl-bin.

Perhaps this was the case on your install?  Let me know either way...

------- Comment #3 From Geoff Cant 2003-10-01 22:14:31 0000 ------- 
Ok, my first build must have just broken then - if I remerge it now, it all
installs fine. Inetd was running when I merged it last time, the package
just didn't install a lisp.core for some reason.

No problems now.