In this version, libgpgme-pthread.so has been removed in favor of just
using libgpgme.so as the thread-safe library. PORTREVISION has been
bumped on all ports depending on security/gpgme so that any that may have
linked to -lgpgme-pthread will link to -lgpgme instead.
The Python module provided by security/py-gpgme has been renamed upstream
from pyme3 to gpg. This removes the conflict with security/py-pyme,
although security/py-gpgme is still the direct replacement of that
module.
- Rewrite the rc script with new options that allows users to:
- set config file.
- set datadir.
- set bitcoin limits.
PR: ports/213235
Submitted by: Christopher Hall <hsw@bitmark.com>
Approved by: maintainer timeout (1 month)
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.
X11 dependencies were added to resolve a crashing issue in newer
versions of sonarr. This has been resolved upstream and is now optional.
The role of X11 (libgdiplus) is to enable image file resizing.
PR: 214244
%%QT_BINDIR%% and %%QT_LIBDIR%% represent the relative location of the
Qt binaries and libraries respectively -- they are only 'bin' and 'lib'
by chance, and should not be used that way.
Approved by: portmgr (blanket), rakuco (mentor)
By popular demand split out deluge onto CLI part and GUI part to let users with
headless servers or users who do not want to install all the GTK2 stuff install
just deluge with minimal required dependencies.
deluge-cli port was introduced, that let user to run in CLI mode and to control
the queue via web-interface.
This change requires all the users of net-p2p/deluge to deinstall it first and
then install the required part:
- net-p2p/deluge-cli if GTK2 GUI is not required
- net-p2p/deluge to get the graphical client (net-p2p/deluge-cli will be
installed as a dependency)
Requested by: many
It was reported by many people that python binding fails to import after
updating to 1.1.1, breaking net-p2p/deluge runtime at least.
Bump PORTREVISION to initiate packages rebuild.
Fix is based on this commit:
https://github.com/voidlinux/void-packages/commit/e3a19958
PR: 213739
Reported by: many
Approved by: portmgr (just-fix-it blanket)
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.
- Lots of changes, see link to the Changes
- Fixed QT option (RADIO->SINGLE), see details in PR#208038
- Changed Qt default to Qt5
PR: 209132
Changes: http://www.qbittorrent.org/news.php
Submitted by: Yuri Victorovich <yuri@rawbw.com> (maintainer), mi, matthew@reztek.cz
To avoid confusion, the main port is to track the latest release.
Whether to rename includes/libraries as well making it possible to
install 2.x and 3.x side-by-side remains to be investigated.
PR: 210505 (for tracking)
Inspired by: PkgSrc
USES=localbase:ldflags can be used to set LDFLAGS. Normally LDFLAGS
appears too early on the command line causing some ports to link with
their own libraries in LOCALBASE (if installed) instead of WRKSRC.
Also make use of _USES_POST so -L${LOCALBASE}/lib is added as late as
possible after anything a port Makefile might set. Use _USES_POST
instead of .include in libedit.mk and libarchive.mk so things like
'USES=libedit localbase:ldflags' work correctly.
Fix some issues with LIBS in some ports.
Switch ports that don't support LIBS to localbase:ldflags.
PR: 212987
Exp-run by: antoine
Approved by: portmgr (antoine)
- Clean up the Makefile.
- Follow some upstream recommendations (--with-data-packaging=archive,
--disable-renaming, -DICU_NO_USER_DATA_OVERRIDE).
- Patch makefiles to install static libraries with INSTALL_DATA so they
aren't stripped.
- Patch config/mh-bsd-gcc to sync with config/mh-linux-gcc.
- Fix endianness detection in ICU. The code wanted to use BYTE_ORDER
defined in machine/endian.h, but this isn't visible because ICU is
compiled with _XOPEN_SOURCE. Patch the code to use _BYTE_ORDER instead.
- Compile ICU with C++11 compiler to enable move constructors.
- Patch ICU to fix a problem with atomics in the case of a C++11 compiler
without C++11 header <atomic> (like Clang on FreeBSD 9).
- Bump all ports that depend on it due to library version change.
- Add USES=compiler:c++0x to some ports that pick up -std=c++0x from ICU
pkgconfig files.
- Add USES=compiler:c++11-lib to graphics/libcdr01 because it also needs
a C++11 runtime library now. Add this to all ports that depend on it
so their executables load the right libstdc++.so on FreeBSD 9.
PR: 205120
Exp-run by: antoine
Approved by: portmgr (antoine)
Zetacoin explicitly fails to configure when libressl is detected. It can
only be built with OpenSSL right now (similar to litecoin).
Approved by: SSL blanket
In file included from app/application.cpp:70:
In file included from ./base/bittorrent/session.h:43:
./base/bittorrent/torrentinfo.h:50:37: error: no type named 'intrusive_ptr' in namespace 'boost'
explicit TorrentInfo(boost::intrusive_ptr<const libtorrent::torrent_info> nativeInfo = boost::intrusive_ptr<const libtorrent::torrent_info>());
~~~~~~~^
./base/bittorrent/torrentinfo.h:50:50: error: expected ')'
explicit TorrentInfo(boost::intrusive_ptr<const libtorrent::torrent_info> nativeInfo = boost::intrusive_ptr<const libtorrent::torrent_info>());
^
./base/bittorrent/torrentinfo.h:50:29: note: to match this '('
explicit TorrentInfo(boost::intrusive_ptr<const libtorrent::torrent_info> nativeInfo = boost::intrusive_ptr<const libtorrent::torrent_info>());
^
./base/bittorrent/torrentinfo.h:80:16: error: no type named 'intrusive_ptr' in namespace 'boost'
boost::intrusive_ptr<libtorrent::torrent_info> nativeInfo() const;
~~~~~~~^
./base/bittorrent/torrentinfo.h:80:29: error: expected member name or ';' after declaration specifiers
boost::intrusive_ptr<libtorrent::torrent_info> nativeInfo() const;
~~~~~~~~~~~~~~~~~~~~^
./base/bittorrent/torrentinfo.h:83:16: error: no type named 'intrusive_ptr' in namespace 'boost'
boost::intrusive_ptr<libtorrent::torrent_info> m_nativeInfo;
~~~~~~~^
./base/bittorrent/torrentinfo.h:83:29: error: expected member name or ';' after declaration specifiers
boost::intrusive_ptr<libtorrent::torrent_info> m_nativeInfo;
~~~~~~~~~~~~~~~~~~~~^
In file included from app/application.cpp:70:
./base/bittorrent/session.h:291:63: error: no matching constructor for initialization of 'BitTorrent::TorrentInfo'
const TorrentInfo &torrentInfo = TorrentInfo(),
^
./base/bittorrent/torrentinfo.h:51:9: note: candidate constructor not viable: requires single argument 'other', but no arguments were provided
TorrentInfo(const TorrentInfo &other);
^
In file included from app/application.cpp:71:
./base/bittorrent/torrenthandle.h:386:36: error: field has incomplete type 'libtorrent::torrent_status'
libtorrent::torrent_status m_nativeStatus;
^
/usr/local/include/libtorrent/torrent_handle.hpp:72:9: note: forward declaration of 'libtorrent::torrent_status'
struct torrent_status;
^
Reported by: pkg-fallout
- If a port has another upstream, remove GOOGLE_CODE
- If a port only has GOOGLE_CODE mark it BROKEN
Some ports have a local mirror configured but for security reasons, it
is not considered upstream.
Sponsored by: Absolight
If an attempt to build with LibreSSL is made, the configure script emits
this message: configure: error: Detected LibreSSL:
This is not supported, and may break consensus compatibility
Go ahead and mark this port and its slaved with IGNORE when libressl is
used to save the user the trouble of hitting the error later (this is
also done by security/p5-openxpki)
Approved by: SSL blanket
Note for SSL_DEFAULT=libressl:
configure: error: Detected LibreSSL:
This is not supported, and may break consensus compatibility
It might be worth detecting that via SSL_DEFAULT and setting the
port to IGNORE. Or perhaps a newer version of litecoin will support
LibreSSL officially.
Approved by: SSL blanket