[Top][All Lists]

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

Re: guilev2-work [was: LilyPond boolean syntax? \true and \false]

From: David Kastrup
Subject: Re: guilev2-work [was: LilyPond boolean syntax? \true and \false]
Date: Tue, 12 Jan 2016 00:32:05 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

David Kastrup <address@hidden> writes:

> Thomas Morley <address@hidden> writes:
>> 2016-01-11 23:14 GMT+01:00 David Kastrup <address@hidden>:
>>>> Btw, it wasn't entirely clear to me that guilev2.x changes essential
>>>> stuff that often.
>>>> Exactly which guile-version are we aiming for?
>>> The non-existing 2.0.12.  Currently, the stable-2.0 branch.  The main
>>> challenge currently seems to be compiling LilyPond with a Guile version
>>> that is not installed on your system.
>> To be sure, the exercise is:
>> (1) checkout the marked branch
>> ~/guile (master)$ git branch -a
>> * master
> [...]
>>   remotes/origin/stable-2.0
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^
> [...]
>> (2) Compile it
>> (3) Build LilyPond with this guile somehow
>> Correct?
> It's the basis for making more tangible progress.  You can, of course,
> try finding yet another route around all the problems ailing 2.0.11, but
> it's unlikely to continue working in 2.1.

By the way: stable-2.0 is the branch where general development happens.
If you take a look at the commits in master (2.1 development) that
weren't cherry-picks from stable-2.0, the statistics look like:

address@hidden:/usr/local/tmp/guile$ git shortlog -n -s --cherry --since "6 
months ago" origin/stable-2.0...origin
   163  Andy Wingo
     2  Mark H Weaver

2.1 is Andy Wingo's playground.  If you take a look at the Guile
developer list, you'll notice that he does not bother discussing
_anything_ he is doing there.  Sometimes he tells a bit of what he's
doing on his personal blog.

Consequently, all non-compiler and all publicly discussed work is done
in the "stable-2.0" branch.  And that's the one we have to target.

David Kastrup

reply via email to

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