Bug#529331: luatex FTBFS wih libpoppler 0.11 because ~GfxFont() is protected
Some remarks on that ...
On Mi, 20 Mai 2009, Frank Küster wrote:
> in the long run, what does that mean for packages that want to link
> against libpoppler to avoid inclusion of a xpdf copy?
Well, since the switch from 0.8 to 0.10 poppler seems to go away from
compatibility with xpdf. That is bad. First it was the XPDFVERSION that
has disappeared, now the distructor.
> Since this is often done in form of distro patches, not by upstream (at
> least this is the case for *tex), it's the Debian maintainers who need
> to adapt the patches. Thus, we diverge more and more from upstream.
Fortunately, I could convince all upstream of TeX (pdftex, luatex,
xetex) to add support for poppler from 0.10 upwards (I think also 0.8
upwards).
So for example for luatex 0.40.1 there are *no* patches necessary ATM
for sid (poppler 0.10). When there is 0.11 I will have to add new
patches, but we will try to merge them back to upstream as far as
possible.
Still it is a pain that poppler changes APIs ...
> Is poppler upstream aware of this use of their library? What do they
> think about it?
I hope that *someone* can made them aware that now all the TeX programs
are able to use poppler instead per default. Hopefully they think a bit
before changing APIs.
> On the other hand - can you suggest a fix for the issue at hand right
> now?
I guess we have to check the version and simply remove the call to the
destructor.
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at> Vienna University of Technology
Debian Developer <preining@debian.org> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
YADDLETHORPE (vb.)
(Of offended pooves.) To exit huffily from a boutique.
--- Douglas Adams, The Meaning of Liff
Reply to: