On Mon, Dec 10, 2018 at 10:47:11AM +0100, Matthias Kilian wrote:
> [answering to ports@]
>
> On Sun, Dec 09, 2018 at 10:31:21PM +0100, Antoine Jacoutot wrote:
> > On Sun, Dec 09, 2018 at 10:47:46AM -0700, Matthias Kilian wrote:
> > > CVSROOT: /cvs
> > > Module name: ports
> > > Changes by: kili@cvs.openbsd.org 2018/12/09 10:47:46
> > >
> > > Modified files:
> > > print/poppler : Makefile distinfo
> > > print/poppler/patches: patch-poppler_Form_cc
> > > patch-poppler_XRef_cc
> > > print/poppler/pkg: PLIST-main PLIST-qt4 PLIST-qt5
> > > Removed files:
> > > print/poppler/patches: patch-qt5_src_Makefile_in
> > >
> > > Log message:
> > > Update to poppler-0.61.1.
> > >
> > > This is the last version containing qt4 bindings.
> > > Update to 0.72 will happen when I've fixed build
> > > problems of qt4 bindings from 0.61.1 with newer
> > > versions of poppler.
> >
> > Do we really want to keep these bindings?
>
> I don't know. The following ports still seem to use them (according to
> a quick grep through the ports tree):
>
> editors/ktikz
https://github.com/fhackenberger/ktikz/commit/207af3ea668eb8c4cafe46c29a3dfd0363cda679
seems to say it now supports qt5
> editors/texworks
https://github.com/TeXworks/texworks/releases seem to say that qt5 is
supported
> emulators/gr-lida
?
> x11/kde4/kfilemetadata
> x11/kde4/nepomuk-core
> x11/kde4/okular
I assume those 3 will be replaced by their kde5 equivalents :)
> I already have a diff for poppler-0.62.0 where -qt4 is still built
> from the poppler-0.61.1 sources, but starting from poppler-0.63.0,
> problems with the old -qt4 start to begin (access to now protected
> members of some poppler classes), and with newer versions of poppler,
> problems become weird (access to poppler-internal methods with
> changed signatures, complete change from GBool to bool within
> poppler). That would be a hell to maintain.
I dont think you want to go down that road, really :)
No comments:
Post a Comment