Hi Gunnar and Yaroslav,
Please refresh my mind -- is pdftk a strict requirement now for impressive or should still be optional, whenevermupdf-tools (>= 1.5) | poppler-utils would be the tools to require? Gunnar reports that without pdftk he had no luck seeing a presentation.
It's a little more complicated. For *analyzing* the pages, Impressive requires mupdf-tools | pdftk-java. pdftk-java is slightly preferred, because it's required for extracting page titles. Basic page display and hyperlink navigation works with just mupdf-tools though. For *rendering* the PDF to bitmaps, Impressive requires. mupdf-tools | poppler-utils, with a preference for mupdf-tools. In other words, mupdf-tools alone gives you most of the functionality. pdftk is, in that sense, only used for a small, not mission-critical feature (title extraction) at this point. I'm not sure how to translate that into Debian dependencies though. Theoretically, it would be something like "Depends: mupdf-tools | poppler-utils, pdftk-java | mupdf-tools; Suggests: pdftk-java", but I don't know if mentioning the same package twice in Depends is OK, or if a package can be both a dependency and a suggestion. (Also, it's debatable whether pdftk should be a recommendation instead of a suggestion, but I can remember having had this discussion already, and we decided for a suggestion in order to not pull in a whole Java installation by default, so let's keep it at that. perl should definitely be relegated from recommendation to suggestion status though.) The easiest solution certainly would be to make mupdf-tools a hard dependency (i.e. remove the poppler-utils alternative) and call it a day. Best regards, Martin Fiedler
