Pango Update in new binaries

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Pango Update in new binaries

Joshua Nichols
Hello all,

I apologize if this question has already been asked.

Has the new version of pango been ported to the binaries on mac/windows/linux? I noticed here that there has since been bug issues with a previous version that LilyPond has been using, and now there's been fixes to those bugs. I noticed its in the latest dev release of LilyPond, but my question is: is it being retroactively implemented in the stable release?

Thanks,

Josh

_______________________________________________
lilypond-user mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-user
Reply | Threaded
Open this post in threaded view
|

Re: Pango Update in new binaries

Federico Bruni
2015-04-07 19:47 GMT+02:00 Joshua Nichols <[hidden email]>:
Hello all,

I apologize if this question has already been asked.

Has the new version of pango been ported to the binaries on mac/windows/linux? I noticed here that there has since been bug issues with a previous version that LilyPond has been using, and now there's been fixes to those bugs. I noticed its in the latest dev release of LilyPond, but my question is: is it being retroactively implemented in the stable release?


Hi Josh

Nobody replied to you.
According to a recent discussion in this list, it seems that the new Pango version in GUB makes lilypond compile much faster. This would be another good reason to make a 2.18.3 release. Unless 2.20 is close... What developers think about it? (I'm cc-ing lilypond-devel).



_______________________________________________
lilypond-user mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-user
Reply | Threaded
Open this post in threaded view
|

Re: Pango Update in new binaries

David Kastrup
Federico Bruni <[hidden email]> writes:

> 2015-04-07 19:47 GMT+02:00 Joshua Nichols <[hidden email]>:
>
>> Hello all,
>>
>> I apologize if this question has already been asked.
>>
>> Has the new version of pango been ported to the binaries on
>> mac/windows/linux? I noticed here
>> <https://code.google.com/p/lilypond/issues/detail?id=2656> that there has
>> since been bug issues with a previous version that LilyPond has been using,
>> and now there's been fixes to those bugs. I noticed its in the latest dev
>> release of LilyPond, but my question is: is it being retroactively
>> implemented in the stable release?
>>
>>
> Hi Josh
>
> Nobody replied to you.
> According to a recent discussion in this list, it seems that the new Pango
> version in GUB makes lilypond compile much faster. This would be another
> good reason to make a 2.18.3 release. Unless 2.20 is close... What
> developers think about it? (I'm cc-ing lilypond-devel).

I don't think 2.20 is that close: it would be nice to have it work with
GUILE-2.0.  There is rather slow progress on this: the main symptom of
any progress is occasional weird commits to LilyPond, a large amount of
frustration and procrastination on my side that leads to low
responsiveness and productivity of mine, and a number of bug reports of
mine eventually making it into the GUILE issue tracker.

Basically, it's a continuous stream of "oh, that doesn't seem to work
under those circumstances" or "oh, that doesn't seem to work as
intended" with suggestions for alternatives that trip up in different
ways.  And tracking and boiling the new problems down into useful test
routines one can report is not fun.

I am not sure that I'll have every problem in check by the time
GUILE 2.0.12 comes out.

However, it would appear that the 2.18 variant you are envisioning is
basically rather 2.18.3a: identical sources, different build system.

It might be possible to roll something like that if it would help
people.  It would still self-identify as 2.18.3 but the installers would
get a different file name.  No idea how much of a nuisance that would be
for our package providers.  If that trips up procedures all too much,
one might just release 2.18.4 "regularly".  But then the question arises
whether one should incorporate other fixes.

--
David Kastrup

_______________________________________________
lilypond-user mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-user
Reply | Threaded
Open this post in threaded view
|

Re: Pango Update in new binaries

Phil Holmes
In reply to this post by Federico Bruni
----- Original Message -----
From: "Federico Bruni" <[hidden email]>
To: "Joshua Nichols" <[hidden email]>
Cc: "lilypond-devel" <[hidden email]>; "Mailinglist lilypond-user"
<[hidden email]>
Sent: Monday, April 20, 2015 12:14 PM
Subject: Re: Pango Update in new binaries


> 2015-04-07 19:47 GMT+02:00 Joshua Nichols <[hidden email]>:
>
>> Hello all,
>>
>> I apologize if this question has already been asked.
>>
>> Has the new version of pango been ported to the binaries on
>> mac/windows/linux? I noticed here
>> <https://code.google.com/p/lilypond/issues/detail?id=2656> that there has
>> since been bug issues with a previous version that LilyPond has been
>> using,
>> and now there's been fixes to those bugs. I noticed its in the latest dev
>> release of LilyPond, but my question is: is it being retroactively
>> implemented in the stable release?
>>
>>
> Hi Josh
>
> Nobody replied to you.
> According to a recent discussion in this list, it seems that the new Pango
> version in GUB makes lilypond compile much faster. This would be another
> good reason to make a 2.18.3 release. Unless 2.20 is close... What
> developers think about it? (I'm cc-ing lilypond-devel).


I don't think an update to 2.18 just to pick up the updated Pango would be a
good idea.  Updates to stable are there really to correct problems that
slipped through into the previous version, not to provide upgrades.  If the
performance improvement is important, I would suggest using 2.19.18.

--
Phil Holmes


_______________________________________________
lilypond-user mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-user
Reply | Threaded
Open this post in threaded view
|

Re: Pango Update in new binaries

Jim Long
In reply to this post by Federico Bruni
On Mon, Apr 20, 2015 at 01:14:55PM +0200, Federico Bruni wrote:

> 2015-04-07 19:47 GMT+02:00 Joshua Nichols <[hidden email]>:
>
> > Hello all,
> >
> > I apologize if this question has already been asked.
> >
> > Has the new version of pango been ported to the binaries on
> > mac/windows/linux? I noticed here
> > <https://code.google.com/p/lilypond/issues/detail?id=2656> that there has
> > since been bug issues with a previous version that LilyPond has been using,
> > and now there's been fixes to those bugs. I noticed its in the latest dev
> > release of LilyPond, but my question is: is it being retroactively
> > implemented in the stable release?
> >
> >
> Hi Josh
>
> Nobody replied to you.
> According to a recent discussion in this list, it seems that the new Pango
> version in GUB makes lilypond compile much faster. This would be another
> good reason to make a 2.18.3 release. Unless 2.20 is close... What
> developers think about it? (I'm cc-ing lilypond-devel).

I'm not sure whether this is germane to Josh's question, but I'm
running Lilypond 2.18.2 and pango 1.36.8, and haven't noticed any
problems.



_______________________________________________
lilypond-user mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-user
Reply | Threaded
Open this post in threaded view
|

Re: Pango Update in new binaries

Joshua Nichols
In reply to this post by Phil Holmes
Is there not a procedure for builds that use the same version number but import newer (fixed) library? Or is the issue about packagers?

I am currently using a MacPorts build of 2.18.2, which gives the desired output. I also downloaded the 2.19.18 version and am getting great results. I'm just thinking about the benefit for others to finally have the proper kerning in the more regularly downloaded versions.

IC,

Josh

On Mon, Apr 20, 2015 at 9:04 AM, Phil Holmes <[hidden email]> wrote:
----- Original Message ----- From: "Federico Bruni" <[hidden email]>
To: "Joshua Nichols" <[hidden email]>
Cc: "lilypond-devel" <[hidden email]>; "Mailinglist lilypond-user" <[hidden email]>
Sent: Monday, April 20, 2015 12:14 PM
Subject: Re: Pango Update in new binaries


2015-04-07 19:47 GMT+02:00 Joshua Nichols <[hidden email]>:

Hello all,

I apologize if this question has already been asked.

Has the new version of pango been ported to the binaries on
mac/windows/linux? I noticed here
<https://code.google.com/p/lilypond/issues/detail?id=2656> that there has
since been bug issues with a previous version that LilyPond has been using,
and now there's been fixes to those bugs. I noticed its in the latest dev
release of LilyPond, but my question is: is it being retroactively
implemented in the stable release?


Hi Josh

Nobody replied to you.
According to a recent discussion in this list, it seems that the new Pango
version in GUB makes lilypond compile much faster. This would be another
good reason to make a 2.18.3 release. Unless 2.20 is close... What
developers think about it? (I'm cc-ing lilypond-devel).


I don't think an update to 2.18 just to pick up the updated Pango would be a good idea.  Updates to stable are there really to correct problems that slipped through into the previous version, not to provide upgrades.  If the performance improvement is important, I would suggest using 2.19.18.

--
Phil Holmes


_______________________________________________
lilypond-user mailing list
[hidden email]
https://lists.gnu.org/mailman/listinfo/lilypond-user