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 .. 5 6 7 8 9 10 11 Next › Last »

<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.

<deleted-account> commented on 2011-03-07 22:01 (UTC)

With mupdf-darcs (or mupdf-git which I just uploaded) your old PKGBUILD works as well. Only the mupdf package from the repos doesn't provide the required files. Here's the comparison so you know what I mean: % pacman -Ql mupdf mupdf /usr/ mupdf /usr/bin/ mupdf /usr/bin/mupdf mupdf /usr/bin/pdfclean-mupdf mupdf /usr/bin/pdfdraw-mupdf mupdf /usr/bin/pdfextract-mupdf mupdf /usr/bin/pdfinfo-mupdf mupdf /usr/bin/pdfshow-mupdf mupdf /usr/share/ mupdf /usr/share/applications/ mupdf /usr/share/applications/mupdf.desktop mupdf /usr/share/man/ mupdf /usr/share/man/man1/ mupdf /usr/share/man/man1/mupdf.1.gz mupdf /usr/share/pixmaps/ mupdf /usr/share/pixmaps/mupdf.xpm % pacman -Ql mupdf-git mupdf-git /usr/ mupdf-git /usr/bin/ mupdf-git /usr/bin/mupdf mupdf-git /usr/bin/pdfclean-mupdf mupdf-git /usr/bin/pdfdraw-mupdf mupdf-git /usr/bin/pdfextract-mupdf mupdf-git /usr/bin/pdfinfo-mupdf mupdf-git /usr/bin/pdfshow-mupdf mupdf-git /usr/include/ mupdf-git /usr/include/fitz.h mupdf-git /usr/include/mupdf.h mupdf-git /usr/lib/ mupdf-git /usr/lib/libmupdf.a mupdf-git /usr/share/ mupdf-git /usr/share/applications/ mupdf-git /usr/share/applications/mupdf.desktop mupdf-git /usr/share/man/ mupdf-git /usr/share/man/man1/ mupdf-git /usr/share/man/man1/mupdf.1.gz mupdf-git /usr/share/pixmaps/ mupdf-git /usr/share/pixmaps/mupdf.xpm

<deleted-account> commented on 2011-03-07 21:25 (UTC)

Hi Sara, now it builds fine with mupdf-darcs being installed, thanks!

Sara commented on 2011-03-07 18:52 (UTC)

Okay, the problem is fixed, but I probably could improve the elegance of the code (for instance, how do I figure out the current version of mupdf in a neat fashion? I'll look into this soon, myself). What fbpdf needed was some header and lib files from mupdf (the lib file is only produced after compiling mupdf, so I had to add that into the PKGBUILD), which do not install in Arch by default. The other solution would be to get Arch to install those files by default, which I might suggest to the AUR mailing list if others concur. I had to make "include" and "lib" directories in the build folder because fbpdf looks for these developmental files in these folders. Otherwise, I would have to patch the Makefile, which I think is an unnecessary complication. An interesting question would be if this program now works against mupdf-darcs. I don't know if the header files that shipped with the current mupdf differ from the darcs version. If so, I might have to add mupdf-darcs under "conflicts". As I don't use the darcs version of mupdf myself, feedback from others who do would be appreciated. That does it for now. Hope this helps someone.