Bug 177446 - RFE: modification of beagle requirement of xpdf via xpdf subpackaging.
RFE: modification of beagle requirement of xpdf via xpdf subpackaging.
Product: Fedora
Classification: Fedora
Component: beagle (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Depends On:
Blocks: FC5Blocker
  Show dependency treegraph
Reported: 2006-01-10 14:24 EST by Jef Spaleta
Modified: 2007-11-30 17:11 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-18 16:52:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jef Spaleta 2006-01-10 14:24:16 EST
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
applications menus.

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.

Comment 1 Dave Malcolm 2006-01-10 14:38:28 EST
Alternatively, does the poppler source tree contain equivalent utilities?
(adding krh to cc)
Comment 2 Jonathan Blandford 2006-01-10 14:42:27 EST
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.
Comment 3 Jef Spaleta 2006-01-10 15:44:17 EST
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.

Comment 4 Kristian Høgsberg 2006-01-10 16:02:00 EST
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
that happens.
Comment 5 Jef Spaleta 2006-01-10 17:06:12 EST
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?


Comment 6 Kristian Høgsberg 2006-01-11 15:47:41 EST
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.
Comment 7 Bastien Nocera 2006-01-13 06:00:06 EST
See also:

beagle should really use libpoppler directly, and by itself, rather than relying
on pdfinfo.
Comment 8 Ngo Than 2006-01-18 13:08:49 EST
There's now a new xpdf-utils subpackage in rawhide, it only includes the command
line tools.
Comment 9 Ray Strode [halfline] 2006-01-18 16:52:04 EST
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

Note You need to log in before you can comment on or make changes to this bug.