View Single Post
Flandry's Avatar
Posts: 1,559 | Thanked: 1,786 times | Joined on Oct 2009 @ Boston
#1
I have poked at this problem a few times before and always just figured i'd "wait for PR1.2" before worrying about it. Well, PR1.2 is here and my excuses pretty much used up.

I'm really not very knowledgeable about library versioning, nor how that works with repos, and would really appreciate help getting this issue resolved.

Here it is: i'm trying to use libpoppler-qt in an app and the dependencies are broken. It works okay on my N900 after some apt forcing, but it won't go through autobuilder. There seems to be rather a mess with libpoppler in the repos:
libpoppler-dev
libpoppler-glib-dev
libpoppler-glib-ruby
libpoppler-glib-ruby1.8
libpoppler-glib2
libpoppler-glib4
libpoppler-qt4-3
libpoppler-qt4-dev
libpoppler0c2
libpoppler0c2-glib
libpoppler2
libpoppler4
libpoppler5

I was thinking, now that we have Qt 4.6, that it would be a good time to clean out the redundant and/or broken and/or obsolete packages and push libpoppler to the autobuilder once again with all subpackages enabled. The problem is i don't know where to begin and what needs to be done.

Presumably some apps are currently using one or more of the existing library packages, like Evince:
Originally Posted by qwerty12 View Post
Poppler and Evince are optified, but I can't say the same for all of its dependencies.

Oh, and for you Qt people (BOO! HISS!), I've uploaded the latest Poppler with the Qt 4 bindings.
Help, please?
__________________

Unofficial PR1.3/Meego 1.1 FAQ

***
Classic example of arbitrary Nokia decision making. Couldn't just fallback to the no brainer of tagging with lat/lon if network isn't accessible, could you Nokia?
MAME: an arcade in your pocket
Accelemymote: make your accelerometer more joy-ful