John D. Hendrickson schreef:
* cmucl binary names "lisp.core" using strings(1) but you distribute the file as lisp-dist.core.
This is intentional: when the package installs it will compile and then load common-lisp-controller and save a new image as lisp.core.
* only platform is i386
I only have a i386 to build the package on. In future there is a possibility of having other architectures, but for 90% of the users out there x86 is the only architecture that matters. If you want cross-architecture development, please use sbcl.
* startup shows compile corruption due to compiling phase
sorry? Could you give an example?
* site-init doesn't seem to be the origional and look like it loads * itself recursively (that's what happened to me)
This should not happen, could you give a typescript
Are my problems that I installed this from Sarge BEFORE it became official? Because it seems by package file list things would be more or less the same.
The differences between the pre versions and the final 19b seem slight. But I suspect a few of your problems are because you have a mixed non-debian/debian cmucl installation.
1) I see quite allot of diffs of clisp to the networking and password section. Why does cmucl need this?
clisp?
2) what is "asdf" and why isn't it part of the origional distribution?
Please see http://www.cliki.net/asdf
3) why does
cmucl_19a-release-20040728-11.diff
Include diffs to
lisp.core
When lisp.core is cmucl binary that has to be built - a large part of lisp - which - I might add - makes lisp impossible to use if not built with lisp(1) binary?
It the diff contains a lisp.core patch then this is an error of packaging. Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson|