On Mon, Mar 04, 2002 at 02:06:34PM +0000, Christophe Rhodes wrote:
> On Mon, Mar 04, 2002 at 07:39:11AM -0600, William Harold Newman wrote:
> > On Mon, Mar 04, 2002 at 09:26:31AM +0000, Christophe Rhodes wrote:
> > > >From the point of view of we Debianites, it would be nice to have a
> > > release soonish, as the new version "woody" is in the process of being
> > > finalized, and the current released version on alpha is unbuildable
> > > with itself (because the NIL horribleness was fixed in 0.7.1.18). If
> > > this isn't possible, we can of course patch it ourselves, but it would
> > > be nice to know one way or the other.
> > I'm very happy to have SBCL in Debian, and I don't mind accelerating a
> > release to help. Unfortunately right now doesn't seem like a very good
> > time for a release, [snippety]
> I'm no expert on the Debian release process -- I see it mostly from
> the outside.
> What I suggest, given your development plans, is that you don't
> disturb your release plans, and that the Debian maintainer incorporate
> the symbol-hash patch and the environ patch from CVS, since those are
> probably the critical fixes, and should sbcl release before woody then
> the new sbcl release can be pushed woodywards anyway.
Using sbcl-0.7.1.22 (the last CVS version before I started messing
with stack overflow detection, checked in 2002-02-20) would probably
be OK. It's not specially tested as a release, but nothing is known to
be wrong with it. And it has the environ fix so it will run under a
different libc than it was compiled under, which is as you say
probably important for Debian. (I'm not sure what symbol-hash problem
you're referring to. Any recent fixes related to that have slipped my
I could even release 0.7.1.22 myself, somehow retroactively tagging it
as 0.7.2, but I'm disinclined to get into that kind of CVS
bookkeeping/renumbering confusion. So I expect I'll follow your advice
and just keep meandering toward 0.7.2 later in March.
In general, anyone who wants to grab CVS snapshots and/or patches for
release elsewhere is advised to (1) check on this list in case anyone
knows any relevant version idiosyncrasies, and (2) do basic testing on
all their release platforms (at least running SBCL's built in
tests/run-tests.sh script), since I don't have the ability to test on
anything but x86 OpenBSD and x86 Linux, and most of the time I only
test on x86 OpenBSD.
William Harold Newman <william.newman@...>
"Look on my works, ye Mighty, and despair!" -- Ozymandias, King of Kings
PGP key fingerprint 85 CE 1C BA 79 8D 51 8C B9 25 FB EE E0 C3 E5 7C