On Sat, Jan 12, 2019 at 07:18:57PM -0600, Bruce Dubbs via blfs-dev wrote:
>
> How is poppler supposed to get people to stop using things they don't intend
> to be external? Marking things as deprecated is often ignored.
>
> In this case, inkscape was using an internal poppler header to define glib
> constructs. The problem is not with poppler, it is with inkscape.
>
> The only other problem package that I know of is libreoffice. I have not
> built it yet with the new poppler, so we will see if that is a problem. Of
> course we can always fix libreoffice by removing --with-system-poppler.
>
> Looking at the patch we have for libreoffice, it appears that we are just
> changing gTrue to true and GBool to bool. Why is that a poppler issue?
>
TeXLive is also affected, but for that I've given up on trying to
keep up with poppler's machinations - what works for one release
will break in the next-but-one. Hopefully, TeXLive-2019 will not be
using poppler (the main use is apparently in XeTeX or XeLaTeX, if I
understood the list posts correctly).
I think some of the poppler changes are just gratuitous.
Unfortunately, 0.72 turned out to be a vulnerability fix, so
sticking with old shipped versions (TL, LO) might be a bad idea.
The real problem is that people used the xpdf functionality because
it was available (apparently, dealing with the structure of PDFs if
I have understood why it was used).
And it's a poppler issue because they have been changing the true
and bool names in each release. In an ideal world, in the same way
that friends would not let friends use cmake, people would not use
poppler except for very limited cases.
ĸen
--
In my seventh decade astride this planet, and as my own cells degrade,
there are some things I cannot do now: skydiving, marathon running,
calculus. I couldn't do them in my 20s either, so no big loss.
-- Derek Smalls, formerly of Spinal Tap
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
