bug-lilypond
[Top][All Lists]
Advanced

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

Re: wrong version number


From: James
Subject: Re: wrong version number
Date: Mon, 12 May 2014 09:27:31 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0

On 12/05/14 09:21, James wrote:
> On 07/05/14 14:02, James wrote:
>> Hello
>>
>>
>> On 7 May 2014 09:36, Phil Holmes <address@hidden
>> <mailto:address@hidden>> wrote:
>>
>>     "James" <address@hidden <mailto:address@hidden>> wrote in
>>     message news:address@hidden
>>
>>         On 05/05/14 07:53, Han wrote:
>>
>>             I've installed version 2.18.2 but the test.ly
>>             <http://test.ly> displayed 2.16.0.
>>             \version "2.16.0"  % necessary for upgrading to future
>>             LilyPond versions.
>>
>>
>>             _______________________________________________
>>             bug-lilypond mailing list
>>             address@hidden <mailto:address@hidden>
>>             https://lists.gnu.org/mailman/listinfo/bug-lilypond
>>
>>         I'll create a patch/tracker.
>>
>>         James
>>
>>
>>     Reckon this is Welcome_to_LilyPond.ly, and this is something of a
>>     general build problem.  It really should use the version of the
>>     downloaded LilyPond without requiring manual change for every
>>     build.  However, I could in the interim do it every build, so a
>>     tracker and a change to the CG
>>     
>> http://lilypond.org/doc/v2.19/Documentation/contributor/minor-release-checklist
>>     would be a good start.
>>
>>     -- 
>>     Phil Holmes
>>
>>
>> https://code.google.com/p/lilypond/issues/detail?id=3917
>>
>> and
>>
>> https://code.google.com/p/lilypond/issues/detail?id=3916
>>
>> James
>
> I'm wondering now if Tracker 3916 is now pointless. That is if I make
> the change then it will get checked/changed on the next GUB build
> anyway. So if I 'fix' this it makes no difference to master (my change
> was to make the \version STABLE than DEVELOPMENT release).
>
> Let me know and I can abandon this patch.
>
> James
Actually I have seen tha Phil has already updated the two files for
current development, so I have merged 3916 into 3917 just for completeness.

James


reply via email to

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