Pedro Kröger wrote:
Paul Scott <[EMAIL PROTECTED]> writes:
If you're working on the the next lilypond-snapshot would you consider
renaming your current lilypond-snapshot to lilypond or something else
and keeping it available. Feri's version still segfaults on my sid
system.
I haven't work on it in a while. I'm now catching up with latest changes
and will release it pretty son (I hope!)
Great!!
Why would you like to have it renamed to "lilypond"?
Not the new (2.5.x?) that you are working on but the 2.4.2 that you have
already done.
the ideia of having
a "snapshot" package is that it can be installed concurrently with a
stable lilypond version (e.g. 2.4)
Agreed. lily-pond-snapshot would be the latest experimental/development
version (2.5.x) and lilypond would the one (2.4.2) that you now call
lilypond-snapshot. Each time a snapshot version becomes somewhat stable
you could rename it lilypond and work on the newer version as
lilypond-snapshot. From Debian I can only get 2.2.6. I have been using
your 2.4.2 for all my work for several months and don't want to go back
to 2.2.6 if something in lilypond-snapshot is broken.
Thanks,
Paul
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
