[bug#29403] [PATCH] gnu: gcl: Update snapshot.

[Ludovic Courtès]

Kei Kebreau <address@hidden> skribis:

>> Kei Kebreau <address@hidden> skribis:
>>
>>> * gnu/packages/lisp.scm (gcl): Update to 2.6.12-1.5956140.
>>> [arguments]: Remove CFLAGS from make-flags; adjust pre-conf phase.
>>> [native-inputs]: Add which.
>>
>> Could you include a rationale for using a development snapshot?
>> Normally we’d stick to upstream releases, unless there’s a good reason.
>>
>> Thanks,
>> Ludo’.
>
> The short story is that there is an issue with GCL's garbage collection
> when it gets built on hydra.gnu.org.

Do you mean that substitutes disappeared?  (I just tried and got
substitutes from berlin.guixsd.org.)

> In the process of investigating this issue, I noticed that Camm
> Maguire, GCL maintainer, uses these development snapshots in the
> package he oversees for Debian. This specific snapshot is the latest
> one and is shipped in Debian unstable, but even stable uses a fairly
> recent GCL development snapshot. These snapshots are mainly small bug
> fixes and optimizations from the look of the GCL commit history.

OK, that certainly justifies this patch.

Nevertheless, we should also kindly invite them to publish these as
formal releases rather than giving Debian a special treatment.

> If you think this update is permissible, how does the following commit
> message read:
>
>     * gnu/packages/lisp.scm (gcl): Update to 2.6.12-1.5956140.
>     [arguments]: Remove CFLAGS from make-flags; adjust pre-conf phase.
>     [native-inputs]: Add which.
>
>     This update includes small upstream bug fixes and optimizations.

Sounds good, yes.

Thanks for explaining!

Ludo’.