Date: Sun, 03 May 2015 00:04:55 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 199871] [PATCH] x11-themes/qtcurve-* update to 1.8.18 and add -qt5 port Message-ID: <bug-199871-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199871 Bug ID: 199871 Summary: [PATCH] x11-themes/qtcurve-* update to 1.8.18 and add -qt5 port Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: matthew@reztek.cz Keywords: patch Created attachment 156257 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=156257&action=edit x11-themes/qtcurve 1.8.18 update and overhaul QtCurve ports have not been updated in a few years. In that time, upstream has changed maintainers and hosting. The sources for the GTK and Qt ports were unified and support for Qt5 was added in the last release, which was made more than a year ago. The ports have been overhauled to accommodate the upstream changes. There is now a qtcurve-utils port which builds a shared library and translations. All other ports (-gtk2, -kde4, -qt4, -qt5) are slaves of the -utils port. The -utils port is a common dependency and all others can be installed independently of each other. All ports can be built and installed together without conflicts. The further separation brings us to 5 ports. I would have liked to unify everything into a single port with options for each toolkit, but use of Qt4 and Qt5 in a single ports causes conflicts, and that single port would've had quite a few dependencies with all options enabled. Although the separate ports add a bit of build overhead (no more than before), they are more convenient for pkg users. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199871-13>