#8482 closed defect (fixed)
UPDATE: slime-20060419
Reported by: | easye | Owned by: | gwright@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.2 |
Keywords: | Cc: | ||
Port: |
Description
It turns out that slime is usually used against a CVS version, instead of having a release version, so I have updated the Portfile. Now slime will work against all Lisp executables that build within DarwinPorts ('openmcl', 'sbcl', and 'clisp').
The one subtlety here is that we now have the port named 'slime-YYYYMMDD' instead of 'slime-M.m.b' which doesn't seem to upgrade via 'sudo port upgrade outdated'. I suppose we could label the new version as 'slime-2.0' (which it roughly corresponds to, but this seems to be an informal distinction.) Any ideas?
Attachments (1)
Change History (7)
Changed 19 years ago by easye
comment:2 Changed 19 years ago by gwright@…
Owner: | changed from darwinports-bugs@… to gwright@… |
---|
I'll test this. I've already bumped the epoch as noted by Daniel Luke.
I'm also going to add variants for sbcl and clisp. The sbcl variant should help people with macbooks, since it is the only DP lisp that builds on that platform.
-Greg
comment:3 Changed 19 years ago by easye
Why don't we just make 'sbcl' the default Lisp, then?
When I first created the port, 'openmcl' was the only Lisp that I could get Slime to work against. 'sbcl' has repeatedly shown itself to have much better (if rather verbose) error messages, so I have mainly switched over to it.
comment:4 Changed 19 years ago by gwright@…
Resolution: | → fixed |
---|---|
Status: | new → closed |
Mark,
Committed. Thanks!
-Greg
comment:5 Changed 19 years ago by gwright@…
Mark,
OK, I'll change it the default to sbcl.
Best Wishes, Greg
slime-20060419 Portfile