[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] [PATCH] Fix #1133

From: Peter Bex
Subject: Re: [Chicken-hackers] [PATCH] Fix #1133
Date: Fri, 20 Jun 2014 08:22:30 +0200
User-agent: Mutt/

On Thu, Jun 19, 2014 at 11:36:58PM +0200, Kristian Lein-Mathisen wrote:
> Thanks so much for looking into this, and fixing it, Peter! This is
> probably the only patch on chicken-hackers I'll ever understand :) I should
> have thought about using DEBUGBUILD myself. I'll see if I can be of more
> use next time!

Don't worry about it, I always have a debug build lying around :)

> We are depending on this fix for our systems in prod. Will there be a new
> tarball or do we have to build from git for now? What's usually the
> process in a case like this?

Like I said in my mail this should go into stability, from which point
releases are periodically made.  Christian indeed cherry-picked it into
that branch, so it's sitting there waiting for a release.

I don't think this change is so important that it warrants publishing a
new release; I'd prefer to have a few more bugfixes accumulate in the
branch.  You can always choose to build from git from the stability
branch, though.  That way you don't risk building a CHICKEN with any
new unknown bugs.

Have you seen my comment about the known workaround?  You can just
(require-library ports) or (use ports) in your code (even if you're not
using the ports unit).  This will fix the problem by ensuring that the
ports unit is loaded before running the program.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]