Bug#605871: [Pkg-fonts-devel] Bug#605871: Bug#605871: fontforge runs find / during the configure step

2013-04-15 Thread Khaled Hosny
On Mon, Apr 15, 2013 at 04:46:42PM +0900, Hideki Yamane wrote: > On Mon, 15 Apr 2013 09:16:12 +0200 > Fabian Greffrath wrote: > > If this configure options is only relevant for building the bundled > > freetype copy, then it should be alright as it currently is. The > > freetype system library in

Bug#605871: [Pkg-fonts-devel] Bug#605871: Bug#605871: fontforge runs find / during the configure step

2013-04-15 Thread Khaled Hosny
On Mon, Apr 15, 2013 at 03:22:26PM +0800, Paul Wise wrote: > On Mon, Apr 15, 2013 at 2:44 PM, Hideki Yamane wrote: > > > --with-freetype-src option should be used with relevant path like > > "--with-freetype-src=/foobar". But anyway, freetype source file is > > necessary to include to build wit

Bug#605871: [Pkg-fonts-devel] Bug#605871: Bug#605871: fontforge runs find / during the configure step

2013-04-15 Thread Hideki Yamane
On Mon, 15 Apr 2013 15:27:12 +0800 Paul Wise wrote: > > No, definitely not. Please fix ttf-kochi too, it shouldn't copy > > freetype around either. > > Please do fix ttf-kochi though. No, I've said ttf-kochi is just an example for multiple upstrearm tarball and not including freetype source, s

Bug#605871: [Pkg-fonts-devel] Bug#605871: Bug#605871: fontforge runs find / during the configure step

2013-04-15 Thread Paul Wise
On Mon, Apr 15, 2013 at 3:22 PM, Paul Wise wrote: > On Mon, Apr 15, 2013 at 2:44 PM, Hideki Yamane wrote: > Please file a bug against freetype asking for them to do either of these: Please ignore what I wrote here, Fabian is correct. >> Q: Should we include freetype source with fontforge? >>