Re: LSR is not at the stable release level

[Eluze]

Thomas Morley wrote
> seems you *really* want the LSR at 2.16. :)

I consider the LSR a valuable addition to the regular LilyPond and I have
used a lot of those snippets - sometimes I changed a little bit sometimes I
used the original. now if I can't use the solutions I have elaborated some
time ago - and I believe many other users have benefited from this source -
I will have to be very careful about relying to these snippets: I can't
update them with convert-ly and I have no Scheme skill to make them work
again. (just thinking if the LSR should not be checked against regressions
before a new version can be released - I know this would delay releases by
days or weeks, but in the end you're looking for a better release and not
for more trouble.)

> There are two reasons not to update now:
> 
> b) It seems that _any_ change to the code of a snippet will result in
> a strange LSR-image. That was the reason I stopped adding commented
> 2.16.-code, as I mentioned before.
> 
> So, what should we do?
> 
> Any Idea?

- has anybody an idea why these strange output files are created?
- are there alternatives to host a collection of additional snippets - I
must confess I like the actual form, even if there are a few things to
improve.
- start a new issue?

Eluze




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/LSR-is-not-at-the-stable-release-level-tp133838p134128.html
Sent from the Bugs mailing list archive at Nabble.com.