SBCL 1.1.7 okay with Quicklisp?

[djw]

I recall that last month's SBCL 1.1.6 release had conflicts with some Quicklisp functions. 

Has anyone investigated the soon-to-be-released SBCL 1.1.7 to determine if those conflicts are resolved and no new dramas occur?

_don

[Zach Beane]

I've built the Quicklisp universe with pre-1.1.7, and there's one minor
incompatibility with the make-hash library. It's fixed in the git repo
of make-hash and the next Quicklisp update will have the fix.

That's all I found.

Zach

[Donald Winiecki]

What is the release cycle for Quicklisp?

_don

> --
> You received this message because you are subscribed to a topic in the Google Groups "Quicklisp" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/quicklisp/RpivtNCaHOk/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to quicklisp+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Zach Beane]

Donald Winiecki <dwin...@boisestate.edu> writes:

> What is the release cycle for Quicklisp?

I try to update the libraries once per month.

Zach

[Donald Winiecki]

Thanks for all of your work to support us!

I note that an update to QL libraries occurred about a week ago.
Should I expect updates to appear about the middle of any given
calendar month?

_don

[Zach Beane]

I try to make updates on the first weekend of each month, but it doesn't always work out that way.

Zach

You received this message because you are subscribed to the Google Groups "Quicklisp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quicklisp+...@googlegroups.com.

[Donald Winiecki]

Thanks. If I add these lines to my .sbclrc, will I it always succeed
in pulling in the new dists, and client update when launching SBCL (at
the terminal or with SLIME) or is there something interactive that
means I should run these separately from a REPL?

;;; Automatically get updated Quicklisp files, if available
;;; from http://www.quicklisp.org/beta/#installation
(ql:update-all-dists)

;;; Automatically get updated Quicklisp client, if available
;;; from http://www.quicklisp.org/beta/#installation
(ql:update-client)

_don

[Zach Beane]

Donald Winiecki <dwin...@boisestate.edu> writes:

> Thanks. If I add these lines to my .sbclrc, will I it always succeed
> in pulling in the new dists, and client update when launching SBCL (at
> the terminal or with SLIME) or is there something interactive that
> means I should run these separately from a REPL?
>
> ;;; Automatically get updated Quicklisp files, if available
> ;;; from http://www.quicklisp.org/beta/#installation
> (ql:update-all-dists)
>
> ;;; Automatically get updated Quicklisp client, if available
> ;;; from http://www.quicklisp.org/beta/#installation
> (ql:update-client)

They are normally interactive, but you could add :prompt nil or wrap in
ql-util:without-prompting.

I'm not sure why you might want to always update things like that,
though. I only update when there's something I know I need in a new
version of a library.

Zach

[Donald Winiecki]

Your implication is well-taken. I'm a bit of a fuss when it comes to
maintaining my tools but it surely can shift one's focus from
working-WITH-tools to working-ON-your-tools, so you can get back to
the first part...

_don

[Tom Emerson]

The downside of automatically updating every time you start SBCL is that you could end up with a situation where your stable set of libraries gets frotzed after an SBCL or QuickLisp update. Sometimes packages change in incompatible ways (didn't this happen with Hunchentoot at one point) and you want to have control over that.

Just my $0.02, fwiw.

    -tree

You received this message because you are subscribed to the Google Groups "Quicklisp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quicklisp+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
Tom Emerson
trem...@gmail.com
http://www.dreamersrealm.net/tree

[Donald Winiecki]

Roger that.

Best to check with the list before such a move. I'll keep those
update lines out of my .sbclrc

_don

[Zach Beane]

Tom Emerson <trem...@gmail.com> writes:

> The downside of automatically updating every time you start SBCL is that
> you could end up with a situation where your stable set of libraries gets
> frotzed after an SBCL or QuickLisp update. Sometimes packages change in
> incompatible ways (didn't this happen with Hunchentoot at one point) and
> you want to have control over that.

This is true, but I think mitigated by the ability to go back to a
previous comprehensive set of Quicklisp libraries fairly easily.

Zach

[Tom Emerson]

On Fri, Apr 26, 2013 at 12:40 PM, Zach Beane <xa...@xach.com> wrote:

This is true, but I think mitigated by the ability to go back to a

previous comprehensive set of Quicklisp libraries fairly easily.

True enough. Speaking of which, is there a command to toss unneeded packages? After a couple of years my quicklisp/dists/quicklisp/{archives,software} is pretty noisy with old versions of packages I'll never use.

    -tree

[Zach Beane]

Sorry about that. I need to make it automatic, but until then, you can do something like this:

  (map nil 'ql-dist:clean (ql-dist:all-dists))

Zach

--