Date: Mon, 16 May 2016 16:17:01 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 209556] security/pinentry Message-ID: <bug-209556-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209556 Bug ID: 209556 Summary: security/pinentry Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: makc@FreeBSD.org Reporter: nolden@kde.org Assignee: makc@FreeBSD.org Flags: maintainer-feedback?(makc@FreeBSD.org) Created attachment 170368 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D170368&action= =3Dedit svn diff against ports HEAD for pinentry and pinentry-qt5 Request: add a pinentry-qt5 frontent for pinentry with the according port a= dded and the pinentry port updated. Until now, pinentry only provides a Qt 4 interface although a Qt 5 version = is doable. I added the according options and used the suffix configure option = to rename the qt4 version binary to pinentry-qt4 and use suffix=3D5 for naming= the Qt 5 version pinentry-qt5 to avoid collisions. As freshports.org doesn't show any dependencies on the pinentry-qt4 port th= at would require additional measures for the name change of the provided file (pinentry-qt to pinentry-qt4), I assume it is safe to just rename the binar= y, see https://www.freshports.org/security/pinentry-qt4/ The update covers: - additional Qt5 option to the pinentry port with the according changes required for building with either Qt4 or Qt5 together with Qt5 dependencies - new port "pinentry-qt5" which is basically a copy of the pinentry-qt4 port updated for Qt5. --=20 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-209556-13>