- Create x11-wm/awesome3 for users who want to keep running 3.5.x because
API is not backward compatible
- Add UPDATING note
- Set EXPIRATION_DATE on x11-wm/awesome3 to 6 months, it's enough time for
users to convert configuration files to 4.x
Differential Revision: https://reviews.freebsd.org/D10341
The three elasticsearch beats ports have merged into one single port
systuils/beats that installs all of the above and some more. The reason is to
make the port more maintainable and also that the new heartbeat beat would
conflict with sysutils/heartbeat.
Add heartbeat beat.
Install utilities
share/beats/import_dashboards
share/beats/migrate_beat_config_1_x_to_5_0.py
Fix problems with the default configurations [1]
PR: 217081 [1]
* Update Qt5 to 5.7.1
* Move Qt4 binaries to lib/qt4/bin
* Move Qt5 libraries to lib/qt5/lib
By moving the libraries we should finally be able to get rid of the inplace
upgrade bug (see ports bugs 194088, 195105 and 198720): when Qt5's libraries
were lying in /usr/local/lib, which would often get added by pkgconfig to the
linker paths via dependencies, the already installed libraries were linked
against, instead of the ones that were being built. This forced us to make
sure, that -L${WRKSRC}/lib was always coming before -L/usr/local/lib in the
linker flags. With this change this should no longer be the case.
* Rename some ports to match the rest (foo-qtX -> qtX-foo)
* Depend on new port misc/qtchooser [see UPDATING & CHANGES]
There are several new Qt5 ports which all have been created by Marie Loise Nolden
<nolden@kde.org>. Thanks again.
PR: 216797
Exp-Run by: antoine
Reviewed by: rakuco, mat, groot_kde.org
Approved by: rakuco (mentor)
Differential Revision: https://reviews.freebsd.org/D9213
In version 3.6.3, Ice started detecting 64 bit platforms by
checking __WORDSIZE. When using C++98/03, __STDC_LIMIT_MACROS isn't
set by default and __WORDSIZE is always set to 32, even if the
required headers weren't included beforehand. Until a proper
fix is available in base (e.g. not setting __WORDSIZE at all if
__STDC_LIMIT_MACROS isn't defined), we detect if C++11 or newer
is used and only rely on __WORDSIZE in this case, otherwise
we fall back to detecting the platform using other macros.
PR: 216609
Reported by: jbeich
- When motion was updated to 4.x, it was overlooked that the default
search path for the configuration files was changed. This was causing
existing configurations to not be read. Fix the port to install
default configuration in correct location and add an UPDATING message
giving users the proper instructions on where to place their existing
conf files. [2]
- Create an empty ${ETCDIR}/conf.d directory that can optionally be used
to dump camera configs in instead of creating separate lines for each
one in motion.conf
- Add some missing PORTDOCS and install with the correct mode
- Make the VIDEO options OPTIONS_RADIO instead of OPTIONS_SINGLE to
allow for netcam only support (suggested in [2])
- Fix bad logic in configure.ac that was causing V4L to not be dectected
when the PWCBSD option was enabled
PR: 216189 [1]
Reported by: Charles P <charlespigott@googlemail.com>
Patched by: <anthony@ury.org.uk>
Obtained from: upstream
PR: 216466 [2]
Reported by: <bakhur@inbox.ru>, tdb@
Pointy hat to: jhale
MFH: 2017Q1 (blanket)
Unfortunately, it's not uncommon for FreeBSD users to not update
their systems timely and thus end up using unsupported FreeBSD
release. These users continue to update ports tree as usual and
expect it to work, either unaware of the release EoL, or not clearly
understanding the consequences, which results in unexpected build
failures, bogus bug reports, attempts to bring back removed legacy
support bits and general discontent.
This change introduces system version check which makes ports refuse
to build anything on unsupported system. This makes users aware of
EoL of their system and makes it clear that no port is guaranteed to
build.
The error message tells how to override the check (by defining
ALLOW_UNSUPPORTED_SYSTEM, in which case it's turned into a simple
warning), additionally stressing that this configurartion is not
supported.
Currently outdated are OSVERSION < 1003000 (pre 10.3-RELEASE) and
1100000 <= OSVERSION < 1100122 (from 11-CURRENT'2013 to 11.0-PRERELEASE)
I expect these to be kept up to date with base system lifetimes,
be updated BEFORE removing any support for outdated release from
the tree and also serve as a reference of which OSVERSION checks
may be removed.
Approved by: portmgr (swills, mat)
Differential Revision: D9210
- Remove unneeded patch
- Add note about the hidden 'MiscSlimTabs' option (it requires Gtk+ > 3.20).
If this option is set, lots of warnings will appear:
Gtk-WARNING **: Theme parsing error: <data>:2:12: 'min-height' is not a
valid property name
Gtk-WARNING **: Theme parsing error: <data>:8:11: 'min-width' is not a
valid property name
OpenVPN has been updated to v2.4.0.
Changes: <https://github.com/OpenVPN/openvpn/blob/v2.4.0/Changes.rst>
openvpn-polarssl has been renamed to openvpn-mbedtls to match the TLS
library's change of name.
The prior versions of the openvpn ports have been preserved in openvpn23
and openvpn23-polarssl, respectively, and are set to expire 2017-03-31.
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.
