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
Comment #7 on issue 963 by Carl.D.Sorensen: check dependency versions
http://code.google.com/p/lilypond/issues/detail?id=963
It seems to me that with 2.16, rather than 2.14, now being the target for
guile 2.0, this should no longer be
marked Critical (unless there are other libraries we want t
Comment #6 on issue 963 by percival.music.ca: check dependency versions
http://code.google.com/p/lilypond/issues/detail?id=963
No it wouldn't -- then people wouldn't be able to take advantage of it
without
spending hours rewriting their scores.
2.16 will use guile 2.0 (unless it's delayed be
Comment #5 on issue 963 by v.villenave: check dependency versions
http://code.google.com/p/lilypond/issues/detail?id=963
IWBN if we could make the guile 2.0 upgrade coincide with our next major
version bump
(aka Lily 3.0), wouldn't it?
--
You received this message because you are listed in t
Comment #4 on issue 963 by hanwenn: check dependency versions
http://code.google.com/p/lilypond/issues/detail?id=963
I suspect it is will be painful to support both 1.8 and 2.0;
I think the smart plan is to wait for 2.0 to come out , and then try to
upgrade lily
to guile 2.0 fully, throwing a
Comment #3 on issue 963 by pnorcks: check dependency versions
http://code.google.com/p/lilypond/issues/detail?id=963
Sure, I'll look into it.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue
Updates:
Owner: pnorcks
Comment #2 on issue 963 by percival.music.ca: check dependency versions
http://code.google.com/p/lilypond/issues/detail?id=963
Let's not wait for guile 2.0. Even if it comes out tomorrow, we should
probably give
it a few months to find+resolve any major bugs.
Comment #1 on issue 963 by pnorcks: check dependency versions
http://code.google.com/p/lilypond/issues/detail?id=963
Guile 2.0 will be coming out relatively soon, and it's unclear to me
whether we will
be able to support Guile 1.8 or earlier due to major incompatibilities with
Guile 1.8.
W
Status: Accepted
Owner:
Labels: Type-Build Priority-Critical
New issue 963 by percival.music.ca: check dependency versions
http://code.google.com/p/lilypond/issues/detail?id=963
Before 2.14, but fairly close to the release, we should check the versions
of libraries and stuff we use. I'm th
15 matches
Mail list logo
