Updates:
Status: Verified
Comment #14 on issue 963 by percival.music.ca: check dependency versions
for 2.14
http://code.google.com/p/lilypond/issues/detail?id=963
I haven't heard any screams from packagers yet, so let's called this done.
_
Comment #13 on issue 963 by percival.music.ca: check dependency versions
for 2.14
http://code.google.com/p/lilypond/issues/detail?id=963
GUB has built most of the architectures (it's on linux-pcc right now); if
these were
going to cause problems, it would have happened by now. For the reco
Comment #12 on issue 963 by v.villenave: check dependency versions for 2.14
http://code.google.com/p/lilypond/issues/detail?id=963
This may not be the most appropriate place to discuss that, but do we still
want to
ship Python 2.4 with the mingw LilyPond build?
(I personally don't care what v
Updates:
Status: Fixed
Labels: fixed_2_13_21
Comment #11 on issue 963 by pnorcks: check dependency versions for 2.14
http://code.google.com/p/lilypond/issues/detail?id=963
Okay, I've finished checking the libraries. I only bumped two of the
minimum versions:
Fontconfig: 2.4.
Comment #10 on issue 963 by pnorcks: check dependency versions for 2.14
http://code.google.com/p/lilypond/issues/detail?id=963
This is my plan:
I will be checking the APIs for
1) Pango
2) Fontconfig
3) Freetype
to make sure we are not using functions in these libraries that break the
minimu
Updates:
Status: Started
Comment #9 on issue 963 by pnorcks: check dependency versions for 2.14
http://code.google.com/p/lilypond/issues/detail?id=963
For sure, we're not bumping Guile or Python, but I'll begin checking
everything else
that has minimum version requirements.
--
You re
Updates:
Summary: check dependency versions for 2.14
Comment #8 on issue 963 by percival.music.ca: check dependency versions for
2.14
http://code.google.com/p/lilypond/issues/detail?id=963
I want somebody to tell me that we don't want to update any libraries [any
more] for
2.14. Th
