@m040601, I might adopt and update that package, even though I am actually not that familiar with those things (either framebuffer or maintaining packages).
Renaming it to "fbpdf-mupdf" ? So that we could have better coordination and two clean separate alternatives, one for only "mupdf" and only for only "poppler" ?
As for this, the Makefile (see the source code on Github) does not build the poppler-based executable by default, so I guess no need to rename it. (meaning only build fbpdf and fbdjvu in that package)
Pinned Comments
xlucn commented on 2022-05-08 09:53 (UTC) (edited on 2024-09-15 14:09 (UTC) by xlucn)
This is the
fbpdf
package but only built with poppler backend. That is, the mupdf version is not built.The idea is to provide ~a small package (around 50KB) without static-linked mupdf library in
fbpdf
~ (now mupdf is installed as shared library libmupdf, so that package won't be large either) a separate package for users who don't use or like mupdf. The executable name is kept asfbpdf2
, as how the upstream dev did to distinguish from mupdf-based executable. That also happens to avoid the conflict with fbida package in official Arch repo.