Arch Linux User Repository

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.

I have e-mailed the fbpdf developer now that mupdf 0.8 is in the repos (and this program will not compile against it, with similar error output relating to fitz.h). Waiting for a reply, now. Sorry for the delay.

I'm not sure which lines you mean by "But reading the lines you specified...". Do you mean "cc -o fbpdf fbpdf.o draw.o -lm -L./lib -lmupdf -lfreetype -ljbig2dec -ljpeg -lz -lopenjpeg"? That's part of the build process. When I try to compile fbpdf-git with mupdf-darcs as dependency, I get cc -c -Wall -Os -I./include fbpdf.c fbpdf.c: In function ‘showpage’: fbpdf.c:80:2: error: too many arguments to function ‘fz_clearpixmap’ /usr/include/fitz.h:625:6: note: declared here make: *** [fbpdf.o] Error 1 Aborting... So the error is a different one.

Thanks for the chroot advice--I might have to try it. But reading the lines you specified... are those normal lines in the build process, or part of the error output you received when trying to compile with mupdf-darcs? If the latter, I might have been wrong about the llpp connection. Here is the error that used to be in llpp (but was fixed): link.c:(.text+0x224a): undefined reference to `fz_clearpixmapwithcolor' I *thought* I saw something similar when compiling (myself) fbpdf with mupdf-darcs. I'll have to try installing the darcs version again, maybe next week (I have two midterms this week), to test. But if you do remember the error output, please let me know if it appeared similar to the one I quoted from llpp's building process. Thanks for the PKGBUILD advice--it definitely helped! Glad you have more students in your future to teach.

Absolutely no problem, I'm glad if I can help out! Especially when you give me the feeling that it improves your abilities to create PKGBUILD files (I'm about to become a teacher, so I enjoy this as often as I can :D those pupils won't give a crap I'm afraid) Like you said, mupdf-darcs was the culprit. I downgraded to mupdf from the repos and now it works. I don't think it's necessary to test all your builds in a chroot, although of course it's no mistake to do so ;) Just run makepkg in a clean folder (where there's just the PKGBUILD file and the others, e.g. the install file etc) and see if it runs. Afterwards check the result with namcap to see if the dependencies are right. Maybe you forget a build dependency, but ... well, there are worse things in the world and this is fixed very fast. I guess it indeed makedepends on more packages, because of that line cc -o fbpdf fbpdf.o draw.o -lm -L./lib -lmupdf -lfreetype -ljbig2dec -ljpeg -lz -lopenjpeg Looks like it makedepends on freetype2, jbig2dec, libjpeg and openjpeg and maybe on something which -lz stands for (I have no idea what that might be). In this case a chroot would be very helpful. I don't have any experience when it comes to man pages, but it looks fine to me, at least it provides a nice list of useful shortcuts. So thanks a lot for finding those shortcuts and for the manpage.

Army, I forgot to address in my last post your problem with compiling the package. Was the problem fixed in your PKGBUILD, or did it still not compile? If the latter, I know for a fact that this program does not compile with mupdf-darcs. It's a bug I'll have to take up with the programmer of fbpdf. llpp had the same bug, and the programmer fixed it very quickly, so I don't think it's that hard to fix. I incorporated your changes into my PKGBUILD because they fixed my very glaring mistakes, but I had tested my pre-corrections PKGBUILD on my own computer, and it had worked. The only thing safer than that, I suppose, is to test building packages in a chroot environment, which I haven't tried doing yet.

I've updated my PKGBUILD to incorporate your changes, and created a man page for the program. Thanks for the helpful criticism, Army. I'm not experienced at all in packaging, but even so, my mistakes, once noted, appeared quite careless! I'm also not experienced in making man pages (this is my first), so helpful criticism would be appreciated. Speaking of the man page, I'm not sure if I needed to document the Ctrl-C shortcut, to terminate the program. And there might be some other keyboard shortcuts I haven't noticed (I haven't read the source code that thoroughly), so if other shortcuts work, please post them here so I can update the man page. Thanks.

Well, your new PKGBUILD doesn't work, please ALWAYS try it out before you upload it here. I edited it to my liking, please use it or use it as an assistance to repair yours. http://codepad.org/sVTOD8kB

Ah, I figured out the syntax for zooming in and navigating pages. For zooming, do ZOOMNUMBER-'z', and for navigating, PAGENUMBER-'g'. Very neat. Also, thought others might appreciate knowing that this program is written by an Archer :).

Basic vim shortcuts work for navigation (h,j,k,l), as well as 'i' for more information about the pdf (zoom level, page number, total number of pages, and filename), 'z' for zoom (that is, if it would work... according to the source code, it should), C-d and C-b for scrolling down and up a page, respectively, and H, J, K, L for the very top, next page, previous page, and very bottom, respectively. Currently, this package will not compile with mupdf-darcs, though I think this is something the programmer can fix. Please offer suggestions for ways to improve my PKGBUILD, as I'm very much a beginner. Thanks Army for pointing out the discrepancy between the package name and the provides line :).