Description of problem:
beagle requires the xpdf package for runtime optional support of pdf metadata
searches using the pdfinfo cli utility that is packaged as part of xpdf package.
The problem is xpdf is also a graphical application which clutters the
The best compromise solution i can think of is to split xpdf into 2 packages
xpdf and xpdf-utils. The xpdf-utils package would carry the cli helper utilities
that beagle uses. This way beagle could require xpdf-utils and the gui
application wouldn't be pull into the menus and into the mime-type database for
other gnome applications.
I'm filing this against beagle to get input from the beagle package maintainer.
If this seems sensible we could both talk to the xpdf maintainer about making
the required adjustments to the xpdf package to split out the cli utilities into
a xpdf-utils. I think debian already does this.
Alternatively, does the poppler source tree contain equivalent utilities?
(adding krh to cc)
or, we could build it from poppler. That has a fork of the xpdf headers in it,
for now. In the long run, we're hoping to drop them, but it should be fine for FC5.
Yes, ideally having the xpdf requirement mutate into a requirement on poppler
would be best. But if that doesn't happen in time for FC5 release, consider a
solution so that beagle doesn't pull in the gui xpdf application into a desktop
install next to evince.
poppler-0.5, which I'll release and build in rawhide in a couple of days, has a
copy of the command line tools from xpdf built against poppler. Then we just
need to change beagle to require poppler-utils. I'll post a heads up here when
hmmm beagle's website lists the pdfinfo as a runtime optional dependancy.
Is it appropriate to single out this one optional runtime dependancy and make it
a hard requirment? ssindex is also listed an optional runtime requirement and
is provided in the gnumeric package in Extras-development. Shouldn't gnumeric be
pulled in as a requirement if pdfinfo is? Its not clear from the beagle website
whether wv, which is also in Extras-development, is a runtime or buildtime
dependancy. I'd love for beagle to be able to index my word and spreadsheet
documents as well as my pdfs, should i file a new RFE to pull wv and gnumeric
back into Core as beagle requirements?
OK, poppler-utils-0.5.0-2.0 is now in rawhide and installs these binaries:
Which all are option compatible with the xpdf equivalents (it's the same code).
Assuming beagle uses one of these for PDF indexing, it should be safe to switch
the xpdf dependency to a poppler-utils dependency. Note that the poppler-utils
package conflicts with the xpdf package.
beagle should really use libpoppler directly, and by itself, rather than relying
There's now a new xpdf-utils subpackage in rawhide, it only includes the command
But that causes conflicts because poppler-utils provides some of those tools, too.
I changed xpdf to depend on poppler-utils and made xpdf-utils only contain
things that don't conflict. Hopefully everything should be fixed in tomorrow's