Andy Wingo writes:
> Hey Guilers,
Hi Andy!
> I didn't push anything specific regarding a freeze, but in practice
> since we're so few, we've been great at just putting in release-worthy
> fixes :)
>
> I would say that we are definitely on track for a 1.9 on the 19th.
Agreed.
> I have a list o
Neil Jerram writes:
> Andy Wingo writes:
>
>> Hi,
>>
>> Some motions were made to switch to LGPLv3. I think it's a good for Free
>> Software if Guile switches to LGPLv3. Shall we update copyrights before
>> Friday's release?
>
> Yes. I'm happy to take care of this this evening.
I believe this
Hey Guilers,
I didn't push anything specific regarding a freeze, but in practice
since we're so few, we've been great at just putting in release-worthy
fixes :)
I would say that we are definitely on track for a 1.9 on the 19th. I
have a list of things to add to the NEWS, which I'm appending to th
Neil Jerram writes:
> "carlo.bramix" writes:
>
>> $ ./pre-inst-guile -c '(display "foo")'
>> Backtrace:
>> In unknown file:
>>?: 0* (begin (eval-string "(display") (quit))
>>?: 1* [eval-string "(display"]
>
> That is weird.
>
> Can we first rule out a problem with your shell? What outpu
"carlo.bramix" writes:
> $ ./pre-inst-guile -c '(display "foo")'
> Backtrace:
> In unknown file:
>?: 0* (begin (eval-string "(display") (quit))
>?: 1* [eval-string "(display"]
That is weird.
Can we first rule out a problem with your shell? What output do you
get from this?
$ set - '(d
