Re: LSR imports and version numbers?

[Trevor Daniels]

Phil Holmes writes Saturday, September 28, 2013 2:19 PM

> From: "David Kastrup" <address@hidden>

>> "Phil Holmes" <address@hidden> writes:
>>
>>> There is a question in my mind as to what a) should bump the version
>>> to: i) current version; or ii) version that the update related to.
>>> Simplest is probably i).
>>
>> Uh, i) is what's currently happening and it's _exactly_ what causes this
>> annoyance.  Any file imported from the LSR (which is at 2.14 or similar)
>> that gets changed at all gets bumped up to current.  Since the imports
>> are a one-way street, we just get an increasingly larger number of files
>> getting bumped up to current on each import.
>
> Ah - OK - I understand now.  I'd forgotten that we always start with "old" 
> files, rather than the most recent "updated" file.  Yes, if we can make 
> option ii) work, it would solve this problem.  I'm in favour.

Option (ii) looks the more sensible one to me too.  Any snippet, not just
those in LSR, is more useful if "version" references the earliest
version of LilyPond that can correctly compile it.

Trevor