The problem is not that they *don't have* poppler, the problem is that some distros don't install the private header files, which correct according to poppler design. So poppler is found, but the compile breaks because it's looking for a header file that's missing.
The appropriate way to use poppler in this circumstance is through poppler-glib. Then, if dependencies (such as poppler-glib) are a concern for a particular distro, they can turn off poppler support. However, if Inkscape wants to have pdf support by default, it should require the appropriate packages by default.
This should also save Inkscape devs trouble in the future when poppler internals change - the glib functions will remain constant.
JF
Ted Gould wrote:
Can we check for this in configure? Then those who have it would get it, and others would not.
--TedOn Mon, 2008-01-28 at 14:34 -0600, Joshua Facemyer / Impressus Art wrote:
I realize this is not going to make me well-liked, but I'd like to bring this subject up again before the next release.
The problem is that on some linux distros (at least Gentoo, I know for certain) there will be broken poppler functionality.
I don't think it's enough to say that we don't want to create more dependencies - if functionality requires a dependency, it's kind of necessary to have that dep.
I know that I can work around it, but I don't think it's a good thing to force people to come up with a workaround for pdf support.
JF
Jeff Kowalczyk wrote:
Joshua Facemyer / Impressus Art wrote:
But then we'll have the perpetual problem of people not having the proper header file, which is unsupported by poppler as a public file.
Considering the importance of PDF functionality (looking over the list archives, back in the summer, bulia said something to the effect that Inkscape was now able to compete with professional apps because of the new pdf stuff) I think the dependency on poppler-glib is not a significant disadvantage, especially if the option to not compile with poppler support exists. (Wasn't there talk recently of having a compile-time switch determine whether to include poppler or internal pdf support? Not a perfect solution, but might help if people are determined to keep deps down.)
Also, I'd guess that many gtk apps which use/will use poppler will depend on poppler-glib functions anyway - but I really don't know, so can't say for certain.
The problem here is not just that the missing header prevents functionality. The problem is that it breaks compilation. If poppler is installed correctly (according to poppler devs), and you compile Inkscape with poppler support, it fails.
I understand the need to keep dependencies to a minimum; however, such powerful functionality may merit a new set of dependencies. Maybe it's time to reconsider?
Would it be possible to resolve this issue from inkscape's side of the poppler issue soon?
I've been using inkscape-0.45.1 for about three months, and I'm eager to resume using the trunk, especially in the run-up to 0.46. Thanks.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel