lilypond-user
[Top][All Lists]
Advanced

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

Re: http://lilypond.org/help-us.html afunctional


From: David Kastrup
Subject: Re: http://lilypond.org/help-us.html afunctional
Date: Thu, 05 Jul 2018 20:49:12 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

Graham Percival <address@hidden> writes:

> On Wed, Jul 04, 2018 at 08:21:25PM +0200, David Kastrup wrote:
>> "Phil Holmes" <address@hidden> writes:
>> > I'm slightly surprised that the build picks up the location of those
>> > pages from that part of the version, but obviously it does.  A simple
>> > fix for the next build would be to align the versions given by the two
>> > expressions, but could you have a think about why those pages pick up
>> > different locations from all the others?
>> 
>> I am just as surprised as you are.  I would have thought that the
>> VERSION_STABLE and VERSION_DEVEL lines are exactly used for figuring out
>> the web sites to link to while MAJOR_VERSION/MINOR_VERSION/PATCH_LEVEL
>> is what gets baked into the binary.
>
> Commit 70adadcf60fa2571d3148115af5d7e96d80d57a5.
>
> I suspect that the issue is that we only want a string in the form
> "2.19", and it was easier to create such a string by concatenating
> MAJOR_VERSION and MINOR_VERSION, instead of taking VERSION_STABLE
> of "2.19.65" and removing the final ".xy"

Hm.  I've done a change using VERSION_DEVEL locally but I am not sure
whether there is one valid strategy for both development and stable
releases.

I am not sure I understand the problem.

-- 
David Kastrup



reply via email to

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