Re: Issue 963 in lilypond: check dependency versions for 2.14
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. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions for 2.14
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 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. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions for 2.14
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 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 :) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions for 2.14
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.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. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions for 2.14
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 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. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions for 2.14
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 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 notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions for 2.14
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. 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. -- 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 notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions
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 to check, as well). -- 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 notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions
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 beyond reasonable expectations). Then we can have a few months of stabilization with it before 3.0. -- 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 notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions
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 the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions
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 away backward compat: there are a number of improvements, most notably the Boehm GC which will obviate all the hairy GC handling inside LilyPond. -- 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 notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions
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 notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions
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. Could you do a check for these items now? I'd rather get any dependency update pains out of the way now. -- 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 notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 963 in lilypond: check dependency versions
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. 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. -- 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 notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 963 in lilypond: check dependency versions
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 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. -- 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 notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
