Re: Evolutionary User Strategery

[Erik Sandberg]

On 7/9/06, Fairchild <address@hidden> wrote:
> New scores could use new features and not have to work around the bugs of
> earlier versions.  Older scores that have been carefully tuned, compensating
> for earlier bugs, would continue to produce the intended result without
> having to be overhauled.  There would be no need to maintain multiple
> versions.

This basically implies that all old versions of lily must be included
in the new versions, so e.g. lilypond 2.10 will contain both version
2.10, 2.8, 2.6 and 2.4. Which means that the lilypond package grows by
a factor 4. I think a better solution would be that you create a
script locally, which parses the input ly file, reads the \version
statement, and picks which lilypond version to use to compile your ly
file.

Erik