[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#27152: deprecation warnings with Guile 2.2.2
From: |
Maxim Cournoyer |
Subject: |
bug#27152: deprecation warnings with Guile 2.2.2 |
Date: |
Fri, 02 Jun 2017 21:43:05 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Hi Mark,
Mark H Weaver <address@hidden> writes:
> Maxim Cournoyer <address@hidden> writes:
>
>> On Wed, May 31, 2017 at 2:00 PM, Ludovic Courtès <address@hidden> wrote:
>>
>> Ricardo Wurmus <address@hidden> skribis:
>>
>> > I get a couple of deprecation warnings with Guile 2.2.2, for example
>> >
>> > Import (ice-9 threads) to have access to `current-processor-count'.
>> > `_IOFBF' is deprecated. Use the symbol 'block instead.
>>
>> We can fix the first one with #:use-module (ice-9 threads).
>>
>> The second one is just a pain: in 2.2 one is supposed to write
>>
>> (setvbuf port 'block)
>>
>> instead of
>>
>> (setvbuf port _IOFBF)
>>
>> So we could do:
>>
>> (cond-expand (guile-2.2 (define _IOFBF 'block))
>> (else #t))
>>
>> in some central place (that doesn’t exist), but really, that’s annoying.
>>
>> So I’m tempted to do nothing.
>>
>> Note that normally users do not see these deprecation warnings at all.
>>
>> Thoughts?
>>
>> Why not let good old sed have a run at it? Seems like a simple find and
>> replace operation, and 'block looks nicer than _IOFBF to my eyes.
>
> If we did that, then Guix would stop working with guile-2.0. Given that
> guile-2.2 is not yet available from many popular distros, I think it
> would be unwise to drop guile-2.0 at this time.
Isn't Guile included in the Guix binary releases? I would have thought
so. Otherwise, I just tried "guix pack address@hidden" and the resulting
archive is 40 MiB.
I'm not saying it's worth it, but it's an option.
Maxim