You are not logged in.
- Topics: Active | Unanswered
#1 2010-10-19 00:16:03
- ConnorBehan
- Package Maintainer (PM)
- From: Long Island NY
- Registered: 2007-07-05
- Posts: 1,359
- Website
Evince / epdfview popper version
I run a custom build of evince to get rid of the GNOME dependencies but one of the annoying parts is that I always have to recompile it when I get a new version of poppler. Strangely I can safely upgrade poppler without having to rebuild (or pacman -S) epdfview. It can still read pdf files from the old version. Why is evince more version dependent?
6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.
Offline
#2 2010-10-19 08:11:04
- JGC
- Developer
- Registered: 2003-12-03
- Posts: 1,664
Re: Evince / epdfview popper version
That all depends on how an application links to poppler. If it links through the bindings, then a rebuild is not needed. If it links to libpoppler.so directly, then a rebuild is needed. Evince uses poppler internals not exposed through poppler-glib, so it needs a rebuild whenever poppler gets a soname bump.
Offline
#3 2010-10-19 17:49:56
- Leonid.I
- Member
- From: Aethyr
- Registered: 2009-03-22
- Posts: 999
Re: Evince / epdfview popper version
That all depends on how an application links to poppler. If it links through the bindings, then a rebuild is not needed. If it links to libpoppler.so directly, then a rebuild is needed. Evince uses poppler internals not exposed through poppler-glib, so it needs a rebuild whenever poppler gets a soname bump.
Interesting... but why is then evince in /extra depends on poppler-glib instead of poppler?
Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd
Offline