KPDF from trunk (that is what will become KDE 4.0) just got switched to use poppler >= 0.5.1
STOP
oKular (that if everything goes well will be KPDF successor for KDE 4.0) will be switched during the week
STOP
We still do not use poppler-qt4 bindings because i have still to get them complete
STOP
Hope to get them complete for poppler 0.5.2
STOP
That does not mean i approve some distros silently patching KPDF from KDE 3.5.x to use poppler
STOP
LET'S GO TO THE STREET AND DO THE POPPLER DANCE
NOW!
STOP
3 comments:
> That does not mean i approve some distros silently patching KPDF from KDE 3.5.x to use poppler
It's not the question, if you approve it, but if it's more work for distributors to patch or to issue one security announcement after the other for multiple packages, instead a single one. When distributors (have to) choose to go ahead, it just shows that upstream doesn't deliver. ;p
So if i don't deliver i'm completely free of ignoring gentoo and kubuntu bugs on bugs.kde.org right?
Because i have more than one bug report that is caused PRECISELY because they suck at that "choose to go ahead" thing and introduce bugs that don't exist on REAL kpdf.
That users are filing invalid bugs directly upstream instead using their distributions bugzilla - or even open bugs at both bugzillas - does unfortunately happen.
Completely ignoring would not be friendly, but at least at Gentoo our users are asked to open bugs at bugs.g.o, instead going directly upstream, so we can have a look at it and may point them upstream then. If you find a odd bug, close it and point them back to us.
I'm sorry that it affects you, but kpdf/poppler is really the only custom patch applied to Gentoo's KDE packages. And that for a good reason.
Post a Comment