Pavel Roskin <[email protected]> writes: > Quoting James <[email protected]>: > >> 'Any chance 'that the forthcoming' Lilypond 2.16 will be accepted in >> Fedora 17' > > Fedora 17 packages Lilypond 2.15.29 currently. In my understanding, > it means that the maintainer believes that a new stable version of > Lilypond will be released before or shortly after Fedora 17. I'm sure > Lilypond 2.16 would be packaged quickly once it's released because, > the maintainer is betting that it will be. > > I tried the version packaged in Fedora 17 on one of the scores and > found it utterly broken (bogus barchecks everywhere), so I upgraded to > the git version of Lilypond.
That sounds like imprudent policy. Packaging an unstable version should only be done by somebody committed to tracking upstream developments well enough to quickly replace the version. 2.15.29 is commit 82e1937780c911be71b439a7d1f2006f058f0490 Author: Graham Percival <[email protected]> Date: Thu Feb 9 13:57:59 2012 +0000 Release: update news. This is quite more than 2 months old. Any process that cranks out such an old development version today is not suited for the updating problems in relation to development versions. > But I would gladly use 2.16 at least on some systems once it's > available in Fedora. Who wouldn't? -- David Kastrup _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
