Re: Patch/issue procedures (was: Randomness in layout)

2015-08-22 Thread David Nalesnik
On Sat, Aug 22, 2015 at 6:00 PM, David Nalesnik wrote: > David, > > On Sat, Aug 22, 2015 at 2:24 AM, David Kastrup wrote: > >> David Nalesnik writes: >> >> [Patch] >> >> Maybe put it up on Rietveld and post a pointer on bug-lilypond? Even >> when it does not make all that much sense to create

Re: Patch/issue procedures (was: Randomness in layout)

2015-08-22 Thread David Nalesnik
David, On Sat, Aug 22, 2015 at 2:24 AM, David Kastrup wrote: > David Nalesnik writes: > > [Patch] > > Maybe put it up on Rietveld and post a pointer on bug-lilypond? Even > when it does not make all that much sense to create a new Google issue > for it, my original suggestion to post patch ser

Re: lilypond does not compile: fontforge version not detected

2015-08-22 Thread Miroslav Ć ulc
hi, this patch fixes the issue. fontforge is now detected and configure script finishes without issue. thanks. Dne 22.8.2015 v 14:25 Masamichi HOSODA napsal(a): >> i attempted to install lilypond- gentoo ebuild but it fails because it >> does not detect fontforge version correctly: >> >> #

Re: lilypond does not compile: fontforge version not detected

2015-08-22 Thread Masamichi HOSODA
> hi, > > this patch fixes the issue. fontforge is now detected and configure > script finishes without issue. > > thanks. > > Dne 22.8.2015 v 14:25 Masamichi HOSODA napsal(a): >>> i attempted to install lilypond- gentoo ebuild but it fails because it >>> does not detect fontforge version c

Re: lilypond does not compile: fontforge version not detected

2015-08-22 Thread Masamichi HOSODA
> i attempted to install lilypond- gentoo ebuild but it fails because it > does not detect fontforge version correctly: > > # ./configure > ... > configure: creating ./config.status > config.status: creating config.make > config.status: creating config.hh > configure: WARNING: unrecognized op

Patch/issue procedures (was: Randomness in layout)

2015-08-22 Thread David Kastrup
David Nalesnik writes: [Patch] Maybe put it up on Rietveld and post a pointer on bug-lilypond? Even when it does not make all that much sense to create a new Google issue for it, my original suggestion to post patch series to bug-lilypond while we are transitioning seems nonsensical since it's