>> Please let me know of your comments!
>
> I'm very happy that you got Guile 3.0 working on Windows. Kudos for
> that (and I guess we need to send big thanks to Mike Gran too).
+1
> What I don't really understand is why you want to add compatibility
> with Guile 3.0.x for small x. [...]
I th
Le lundi 06 novembre 2023 à 01:11 +0100, David Kastrup a écrit :
> I have not checked recently, but last time I looked, Guile's versioning
> system more or less worked so that the development branch (and the
> corresponding versions) was Andy Wingo's playground. It was not
> concerned with APIs in
Jean Abou Samra writes:
> What I don't really understand is why you want to add compatibility
> with Guile 3.0.x for small x. Upstream completely breaks the normal
> expectation from what you would find in a point release, by putting
> features and even severely backwards incompatible changes (li
On Sun, 2023-11-05 at 22:48 +0100, Jean Abou Samra wrote:
> What I don't really understand is why you want to add compatibility
> with Guile 3.0.x for small x. Upstream completely breaks the normal
> expectation from what you would find in a point release, by putting
> features and even severely ba
Le dimanche 05 novembre 2023 à 22:36 +0100, Jonas Hahnfeld via Discussions on
LilyPond development a écrit :
> Please let me know of your comments!
I'm very happy that you got Guile 3.0 working on Windows. Kudos for
that (and I guess we need to send big thanks to Mike Gran too).
What I don't re
Hi all,
I hear LilyPond hasn't changed its Guile version since some time (more
than 18 months). So before we get too comfortable with the current
situation, let me propose to move to Guile 3.0. Below is a plan for
that switch, with a transition period to test the official binaries.
Last time, when
