Package Details: fbpdf-git r102.6276360-3

Git Clone URL: https://aur.archlinux.org/fbpdf-git.git (read-only, click to copy)
Package Base: fbpdf-git
Description: A small framebuffer pdf viewer, based on MuPDF.
Upstream URL: https://github.com/aligrudi/fbpdf
Licenses: ISC
Conflicts: fbpdf
Provides: fbpdf
Submitter: Sara
Maintainer: xlucn
Last Packager: xlucn
Votes: 43
Popularity: 0.000000
First Submitted: 2011-02-08 00:46 (UTC)
Last Updated: 2023-11-18 18:26 (UTC)

Dependencies (3)

Required by (0)

Sources (2)

Pinned Comments

xlucn commented on 2022-06-24 05:46 (UTC) (edited on 2023-11-20 08:36 (UTC) by xlucn)

I updated the package. Apart from the fixes (please test it), most notably I removed the poppler-based fbpdf2, and renamed "fbpdf" as "fbpdf-mupdf" instead of "neatfbpdf", still to avoid conflict with "fbida" package. Those are just my own decisions, so they can be changed again.

If you want poppler-based variant, see https://aur.archlinux.org/packages/fbpdf-poppler-git.

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 Next › Last »

<deleted-account> commented on 2011-04-24 13:17 (UTC)

It doesn't build here right now, does it build on your system? Here's my output http://pastebin.com/j6hdygV8

Sara commented on 2011-03-25 22:49 (UTC)

Discovered additional keybindings and nuances to existing keybindings, so the manpage has been updated.

<deleted-account> commented on 2011-03-12 15:29 (UTC)

Perfect, now everything's back to normal :)

Sara commented on 2011-03-11 11:34 (UTC)

Thanks a lot for submitting the bug report, Army. I built mupdf 0.8-2, and fbpdf compiled against it (and I saw the code, which no longer prevents the header files from installing), so I think the problem is indeed fixed. I edited the PKGBUILD for fbpdf accordingly.

<deleted-account> commented on 2011-03-08 13:24 (UTC)

And here it is: https://bugs.archlinux.org/task/23186

<deleted-account> commented on 2011-03-08 13:07 (UTC)

I think mupdf's PKGBUILD goes a little bit against Arch's principles to provide the packages the way they are intended upstream. The PKGBUILD doesn't use "make install", instead the executables are moved to the right places manually (which on the other hand of course is ok for the stuff from the debian folder). That's why these header files and the library aren't included in mupdf from the repos. I'll write a bug report.

Sara commented on 2011-03-07 23:23 (UTC)

In that case, then I should only compile mupdf to build the required files *only if* the user has mupdf from the repos installed, or better yet, take it up with the mailing list. Three measly files, why should it hurt them to add them in? Thanks for the visual file comparison. The old PKGBUILD must work (with -darcs or -git, which have the necessary files) because the developer also made some changes to support the new release. Thanks for the head's up, Army.