[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: xetex on armel - disable or not?



Hi everyone,

On So, 02 Jun 2013, Rene Engelhard wrote:
> Option 3 is probably: "wait". 
> 
> I just uploaded a graphite2 using the patch from
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710336#56.
> Built fine on my armel box.

What is the status wrt harfbuzz at the moment?

On Mo, 03 Jun 2013, Rene Engelhard wrote:
> when I look at the now-successful build of texlive-bin on armel...
> 
> On Thu, May 30, 2013 at 09:10:47AM +0900, Norbert Preining wrote:
> > So that means, that I have two options:
> > * either re-include libgraphite2, too, into the source again and
> >   get a working xetex binary (hopefully) on armel/sparc, too
> 
> .. just out of curiosity: Why is a internal harfbuzz used? :)

There have been several iterations on the harfbuzz side. First I
didn't remove harfbuzz from the texlive-bin source, since it lacked
ICU support in Debian. Then this was added and I removed it again,
until I realized that it did not have graphite2 support on ANY platform.

So at least to have a working xetex binary on all platforms but armel/sparc
I had to keep the harfbuzz library in the texlive-bin sources.

I don't want to lknow what the current status is. I have decided
I will wait at least a month or so, maybe harfbuzz/graphite2/whatever
stabilizes in this time in Debian. I have better things to do but
rebuilding texlive-bin on a daily rythm due to another iteration
of harfbuzz/graphite changes.

I appreciate if you can work that out so that graphite2 and harfbuzz
is usable on all platforms at some point. Until that time, I will
just ignore the issue.

Thanks for your understanding

Norbert

------------------------------------------------------------------------
PREINING, Norbert                               http://www.preining.info
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------


Reply to: