On Sun, Nov 13, 2011 at 06:13:50PM +0100, Antoine Jacoutot wrote: > On Sun, Nov 13, 2011 at 06:06:23PM +0100, Marc Espie wrote: > > On Sun, Nov 13, 2011 at 05:09:51PM +0100, Marc Espie wrote: > > > On Sun, Nov 13, 2011 at 04:47:40PM +0100, Matthias Kilian wrote: > > > > Hi, > > > > > > > > I just looked at the diff from poppler-0.16 (which is eol) to > > > > poppler-0.18. They dropped support for qt3, so updating poppler to > > > > -0.18 will break some kde3 related ports (x11/kde/graphics3, > > > > x11/kde/office3, x11/tellico). > > > > > > > > I could try to disable poppler for these three ports. Any better > > > > ideas? > > > > > > > > CIao, > > > > Kili > > > > > > Well, if you remove poppler support in kdegraphics, you could as well > > > remove kdegraphics... likewise for koffice, it will kill a large part > > > of it. > > Well... unlikely to happen... > > The only solution I see if we do not want to get stuck because of old > unmaintained stuffs is to copy print/poppler to print/poppler016 (or whatever > name), rename/fix the conflicts and adapt these 3 ports to use poppler016, > then update print/poppler to version 0.18. > I can bet some ports will soon require poppler >= 0.18 soon, so better be > proactive about it.
Well, I'll have a look and see if they really dropped poppler-qt3 for a real reason rather than "hey it's old, let's switch to the shiny new shit"... as soon as kili gives me his work...
