|
From: | Rune Zedeler |
Subject: | Re: (patch) extremely minor changes to input/ |
Date: | Mon, 30 Sep 2002 00:55:03 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529 |
Juergen Reuter wrote:
Sorry, that's actually my "fault": I introduced a change in the syntax which is supposed to take effect as soon as the next release will come out. That is why \version really should be 1.6.5 in the next release. Of course, for the moment, you can set it to 1.6.4 for getting everything compiled, but in 1.6.5, it should be \version 1.6.5.
I think that in situations like this, the correct solution would be to alter the patch-level of the lilypond-version - to i.e. 1.6.4.jr1 and then use this as the required version for the input files. After 1.6.5 pops out you could (along with your next patch) also change the requirements of you old files from 1.6.4.jr1 to 1.6.5.
Other suggestions? At least requiring a non-existing version is a Bad Thing (tm). -Rune
[Prev in Thread] | Current Thread | [Next in Thread] |