splitting xpdf
Bug#122786 is a wishlist bug suggesting that the xpdf package be
split up so that the command line utils without huge library
dependencies can be installed on more lightweight systems.
Two questions. Firstly, can anyone recommend a good split?
There are three different sets of dependencies:
xpdf, pdftopbm -- needs xlibs, libpaper, libfreetype, libt1;
pdftops -- needs libpaper
pdfinfo, pdfimages, pdftotext -- just system libraries
libpaperg is pretty light so I think the last two groups
could be combined. pdftopbm doesn't fit real well with
just xpdf as a group, but they share dependencies.
So I was thinking of two packages:
xpdf -- xpdf, pdftopbm (requires xlibs, freetype, t1 etc)
xpdf-utils -- pdftops, pdfinfo, pdfimages, pdftotext (libpaperg only)
Second question: what's the best way to create the packages such
that the binaries don't go missing on existing installations?
Keep an xpdf meta-package depending on two new ones? Or
just live with it?
thanks,
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
Reply to: