===> The following configuration options are available for pinentry-1.3.3:
====> Default frontend: you have to select exactly one of them
EFL=off: EFL frontend
FLTK=off: FLTK frontend
GNOME=off: GNOME frontend
GTK2=off: Gtk+ 2 frontend
NCURSES=on: Curses frontend
QT5=off: Qt 5 frontend
QT6=off: Qt 6 frontend
TTY=off: Console version
===> Use 'make config' to modify these settings
security/pinentry: Update to 1.3.3
Fix typos and ESL.
Use security/gcr as recommended by upstream. Consequently, allow
the security/pinenty-gnome3 child port to build normally.
security/gpgme: Update to 2.0.0
Upstream has split most of the bindings out into separate projects with
this release, so the child ports that were previously providing various
bindings are now autonomous and have new origins. The python bindings
should have been called py-gpg for many years now, since 'gpg' is the
actual module name, so this also corrects that issue.
security/gpgme-cpp -> security/gpgmepp
security/gpgme-qt -> security/qgpgme
security/py-gpgme -> security/py-gpg
gpgmepp and qgpgme have been converted to CMake. py-gpg is now a "fun"
autotools and FreeBSD ports system hybrid. Gpgme, itself, still uses
autotools, but with much less parenting (patching) to do for its
emancipated children.
Adjust several ports to fix API incompatibility with upstream patches
and with some of my own. Adjust all consumers to use the new port
origins of the former child ports.
https://dev.gnupg.org/T7673
security/gcr: Update to 4.3.0
Move the previous version to security/gcr3 and switch consumer ports to it
PR: 282046
Approved by: vishwin
Sponsored by: Future Crew, LLC
security/pinentry-qt6: Fix configure on 13.2
Qt 6.x requires C++17 and the C++ standard is not set for the configure
script nor for the build. The base compiler on FreeBSD 13.2 defaults to
C++11, causing the configure script to fail as would the build if it
made it past the configure stage.
Reported by: pkg-fallout
security/pinentry: Update to 1.3.0
Add security/pinentry-qt6 for the new Qt 6 pinentry frontend.
Make a more generic pkg-message for pinentry frontends that have a
dependency loop with the main port. Previously, only the gnome frontend
had this problem, but a dependency loop was also discovered in the efl
frontend.
https://dev.gnupg.org/T7046
Mk/Uses: always use colon for build/run suffix
Most USES use a colon for build/run(/test) suffixes. Change kde.mk,
qt.mk and pyqt.mk to do the same, and update all ports using that.
Document in CHANGES.
PR: 266034
Exp-run by: antoine
Approved by: tcberner (mentor)
Differential Revision: https://reviews.freebsd.org/D36349
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
security: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* <ports@c0decafe.net>
* Aaron Dalton <aaron@FreeBSD.org>
* Adam Weinberger <adamw@FreeBSD.org>
* Ade Lovett <ade@FreeBSD.org>
* Aldis Berjoza <aldis@bsdroot.lv>
* Alex Dupre <ale@FreeBSD.org>
* Alex Kapranoff <kappa@rambler-co.ru>
* Alex Samorukov <samm@freebsd.org>
* Alexander Botero-Lowry <alex@foxybanana.com>
* Alexander Kriventsov <avk@vl.ru>
* Alexander Leidinger <netchild@FreeBSD.org>
(Only the first 15 lines of the commit message are shown above )
security/pinentry-gnome3: De-version and rename
Due to the new GNOME versioning scheme, security/pinentry-gnome3 has
been renamed to security/pinentry-gnome and all references to
"GNOME 3" have been dropped in favor of just "GNOME". The binary itself
still installs as pinentry-gnome3 at this time, however.
Rename the option GNOME3 -> GNOME in security/pinentry.
PR: 263681
Reported by: PauAmma <pauamma@gundo.com>
security/pinentry*: Update to 1.1.1
Add security/pinentry-efl: An EFL (Enlightenment Foundation Libraries)-based
version of pinentry.
Change the default pinentry program from tty to ncurses so that the package
works out-of-the-box with mail/mutt. [1]
PR: 239381 [1]
Reported by: <heas@shrubbery.net> [1]
Requested by: adamw and Derek Schrock <dereks@lifeofadishwasher.com> [1]
security/pinentry: Users who enable the non-default GNOME3 option will now
have to install security/pinentry-gnome3 manually. This has been done to break
a dependency loop that was introduced in r553735 where security/gcr added a
build dependency on security/gnupg.
Before r553735:
security/gnupg -> security/pinentry -> security/pinentry-gnome3 -> security/gcr
After r553735:
security/gnupg -> security/pinentry -> security/pinentry-gnome3 -> security/gcr
-> security/gnupg
Now:
security/gnupg -> security/pinentry
security/pinentry-gnome3 -> security/gcr -> security/gnupg
A pkg-message has been added to remind users of the GNOME3 option to install the
required package manually and to deinstall it if no longer needed.
PR: 250945
Reported by: <sdalu@sdalu.com>
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Mark QT4 ports/functionality for removal on 2019-03-15
While here, chase some KDE4 ports and functionality, these are scheduled for
removal on 2018-12-31. Change the default option/flavor to QT5 where applicable
or use alternative toolkits like GTK.
Submitted by: tcberner
Reviewed by: adridg, jhale, rene, tcberner
Approved by: portmgr (implicit, flavor hook)
Differential Revision: https://reviews.freebsd.org/D17741
Install texinfo files (GNU info) into ${PREFIX}/share/info
After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.
Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.
Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them
Bump revision of all impacted ports
PR: 232907
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D17816
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
Replace bsd.qt.mk by Uses/qt.mk and Uses/qt-dist.mk
From now on, ports that depend on Qt4 will have to set
USES= qt:4
USE_QT= foo bar
ports depending on Qt5 will use
USES= qt:5
USE_QT= foo bar
PR: 229225
Exp-run by: antoine
Reviewed by: mat
Approved by: portmgr (antoine)
Differential Revision: -https://reviews.freebsd.org/D15540
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
Revision bump of all ports with USE_GL after consolidation of mesa-libs
Approved by: swills (mentor)
Differential Revision: https://reviews.freebsd.org/D10845
Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
security/pinentry-*: Document ncurses requirement
It turns out that every pinentry slave port requires ncurses,
not just -gnome3 and -curses.
Approved by: ncurses blanket
Reassign makc's ports back to the pool.
See "Maintainer Reset" in
https://www.freebsd.org/portmgr/policies_contributors.html. makc's last commit
was in March 31st (r412218), and his ports have been timing out since at least
July (r418155).
I also emailed him 2 weeks ago and have received no response so far.
Bump PORTREVISION in security/pinentry and pinentry-qt4 after r415872.
r415872 changed the binary name that security/pinentry-qt4 installs without
bumping PORTREVISION in the affected ports, so if security/pinentry gets
rebuilt after this change but security/pinentry-qt4 is not the pinentry symlink
will be broken. Similarly, if one builds security/pinentry-qt{4,5} without
updating security/pinentry, the pinentry symlink will also be broken.
PR: 209556
MFH: 2016Q3
New port: security/pinentry-qt5, Qt 5 version of the GnuPG password dialog
PR: 209556
Submitted by: Ralf Nolden <nolden@kde.org> (kde)
Approved by: makc (implicit as kde maintainer)
Update security/pinentry and slave ports to 0.9.7.
From pinentry's NEWS file:
Noteworthy changes in version 0.9.7 (2015-12-07)
------------------------------------------------
* Fix regressions in the Qt pinentry.
* Fix minor problems pinnetyr-tty.
* New option --invisible-char.
Noteworthy changes in version 0.9.6 (2015-09-10)
------------------------------------------------
* Many improvements for the dump tty pinentry.
* Use the standard GTK+-2 text entry widget instead of our outdated
and back-then-it-was-more-secure text widget.
* Use the standard Qt text widget.
(Only the first 15 lines of the commit message are shown above )
GNOME 3 expects pinentry to have libsecret support. so instead of offering
a options change always build it with libsecret support.
Approved by: maintainer (implicit)
- Update to 0.9.5.
- Disable LIBSECRET option for GTK2 by default. It does not work and broke
Thunderbird/Enigmail for me.
Approved by: makc (maintainer)
MFH: 2015Q3
security/pinetry-qt4: set to use c+++11 standard (fixes gcc5)
Unfortunately this still doesn't build on FreeBSD 10 which uses libc++.
It is unknown if it builds on FreeBSD11, but it has been ignored on
FreeBSD11. The main benefit is for gcc5 support right now.
I confirmed that it still builds on FreeBSD 8 and FreeBSD 9.
Approved by: blanket (gcc5)
security/libgcrypt: 1.6.1 -> 1.6.2, bump depends
Changes:
- src/sexp.c (do_vsexp_sscan): Return error for invalid args.
- cipher/md.c (_gcry_md_info): Fix a segv in case of calling
with wrong parameters.
- cipher/primegen.c (_gcry_generate_elg_prime): Change to return an
error code, possible NULL deref in call to prime generator.
- cipher/dsa.c (generate): Take care of new return code.
- cipher/elgamal.c (generate): Change to return an error code. Take
care of _gcry_generate_elg_prime return code.
- ecc: Support the non-standard 0x40 compression flag for EdDSA.
- mpi: Extend the internal mpi_get_buffer.
- mpi: Fix regression for powerpc-apple-darwin detection.
- Fix bug inhibiting the use of the sentinel attribute in src/gcrypt.h.in
(Only the first 15 lines of the commit message are shown above )
security/pinentry:
- Resolve mutual conflict for security/pinentry-* ports
- Add new port security/pinentry-tty for pure console version of pinentry
- Convert security/pinentry to meta-alike port that depends on pinentry-tty by
default and installs commons files (documentation). Mark it architecture
independent.
security/pinentry:
- Check for the presence of libc++ rather than for OSVERSION and
fix options processing [1]
- Use MOC variable provided by bsd.qt.mk
Reported by: wblock [1]
security/pinentry:
- Update to 0.9.0
- Remove pinentry-gtk port (GTK+ 1 support is discontinued upstream)
- Ignore Qt 4 frontend on 10 and greater, it fails to build with clang/libc++
devel/glib12 x11-toolkits/gtk12:
- Convert to USES=libtool and bump dependent ports
- Add INSTALL_TARGET=install-strip
- Remove patches that renamed include directories and libraries so they
didn't conflict with early development versions of glib/gtk 2.0
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav
Update libksba to 1.2.0, and update dependent ports.
The patch also adds a verify target for the PGP signature
of the distfile.
Noteworthy changes in version 1.2.0 (2011-03-01)
------------------------------------------------
* New functions to allow the creation of X.509 certificates.
This release adds features required by the GnuPG 2.1 development
version.
PR: ports/155506
Submitted by: me
Approved by: maintainer timeout
Bump portrevision due to upgrade of devel/gettext.
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
