Menu
▾
▴
#963 check dependency versions for 2.14
Originally created by: *anonymous
Originally created by: percival.music.ca@gmail.com
Originally owned by: pnorcks@gmail.com
Before 2.14, but fairly close to the release, we should check the versions
of libraries and stuff we use. I'm thinking in particular of guile;
there's supposed to be some much-faster version or something.
We don't want to bump version requirements during 2.14.x, so if we're going
to do it within the next 6 months, it should happen within the next 2-3 months.
Marked as Critical because it needs to happen before 2.14, but other than
that this isn't time-sensitive.
Originally posted by: pnorcks@gmail.com
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.
We will also want to enable auto-compilation of LilyPond's Scheme code, and this
feature doesn't exist in Guile 1.8, only in Guile 1.9.something or later.
I think all of the other dependency versions should be okay, but I haven't done a
thorough check yet.
Originally posted by: percival.music.ca@gmail.com
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.
Could you do a check for these items now? I'd rather get any dependency update pains
out of the way now.
Owner: pnorcks
Originally posted by: pnorcks@gmail.com
Sure, I'll look into it.
Originally posted by: hanw...@gmail.com
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 away backward compat: there are a number of improvements,
most notably the Boehm GC which will obviate all the hairy GC handling inside
LilyPond.
Originally posted by: v.villenave
IWBN if we could make the guile 2.0 upgrade coincide with our next major version bump
(aka Lily 3.0), wouldn't it?
Originally posted by: percival.music.ca@gmail.com
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 beyond reasonable expectations). Then
we can have a few months of stabilization with it before 3.0.
Originally posted by: Carl.D.S...@gmail.com
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 to check, as well).
Originally posted by: percival.music.ca@gmail.com
I want somebody to tell me that we don't want to update any libraries [any more] for
2.14. This includes guile, fontconfig, fontforge, font*, texinfo, pango, python, etc
etc etc. We've decided that guile will not be updated for 2.14, but there's still a
lot of things to consider (main on the font side of things).
I've updated the summary.
Summary: check dependency versions for 2.14
Originally posted by: pnorcks@gmail.com
For sure, we're not bumping Guile or Python, but I'll begin checking everything else
that has minimum version requirements.
Status: Started
Originally posted by: pnorcks@gmail.com
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 minimum
versions. If there are any breakages, I will bump versions instead of trying to find
workarounds for older versions. The minimum versions for these three are pretty old
anyway, much older than the versions in Debian stable.
Additionally, I will be (tentatively) bumping the Autoconf minimum version, since
there are a lot of workarounds in stepmake/aclocal.m4 for Autoconf 2.50 that need to
be cleaned up -- I'll take care of that.
Originally posted by: pnorcks@gmail.com
Okay, I've finished checking the libraries. I only bumped two of the minimum versions:
Fontconfig: 2.4.0
Autoconf: 2.60
From what I can tell, our interface would still function with Pango 1.6.0 and
Freetype 2.1.10, so there is no strict need to bump them to newer versions.
I'm done updating dependency versions for 2.14.
Labels: fixed_2_13_21
Status: Fixed
Originally posted by: v.villenave
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 version we do ship, but when I see the size of the
Windows Lily installer I often wish we could strip the bundled Python from all
unnecessary binaries/translations/etc. in order to make it lighter.)
Graham, I'll let you "Verify" this one if that's ok :)
Originally posted by: percival.music.ca@gmail.com
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 record GUB currently
has autoconf 2.63 and fontconfig 2.8.0.
I'll mark it verified once 2.13.21 has officially gone out, in a few days.
The python 2.4 thing is now issue 1079.
Originally posted by: percival.music.ca@gmail.com
I haven't heard any screams from packagers yet, so let's called this done.
Status: Verified