depends on the camlp4 language and labltk ocaml modules, which are
now in separate ports.
- Update x11-toolkits/ocaml-lablgtk2 to 2.18.3
- Update graphics/ocaml-lablgl to 1.05
- Make unison ports use USE_OCAML
- Convert ports to the new flags where needed
- Bump PORTREVISION on ports depending on ocaml-lablgtk2, those need to be rebuilt
PR: 199845
Submitted by: jbeich@
Differential Revision: https://reviews.freebsd.org/D2434
Approved by: portmgr (mat)
databases/cego: 2.21.1 -> 2.22.0
databases/p5-DBD-cego: 1.2.9 -> 1.3.0
lfcbase:
- Added syslog support
- syslog is enabled per default
cego:
- fix in CegoFieldValue::comp for correct null value ordering
- adapt to lfcbase 1.6 with syslog support
p5-DBD-cego:
- adapt to lfcbase 1.6 with syslog support
Submitted by: Björn Lemke <lemke@lemke-it.com>
The -Werror flag reappeared on the latest version, and it still doesn't
build without error on GCC5. In this case, the FLAGS_env variable was
defined and not used tripping [-Werror=unused-variable]
I would seriously remove -Werror from this port (again), but this patch
makes it build again on DragonFly, at least for the moment.
- Update to 2.1.7
- Assign maintainership to Harrison Grundy
PR: 199831
Submitted by: Harrison Grundy <harrison.grundy@astrodoggroup.com>
Approved by: maintainer timeout (more than three in a row)
- Update courier-imap to 4.16.1
- Update maildrop to 2.8.2
- Update sqwebmail to 5.8.2
- Update courier-authlib to 0.66.2
- Some plist and Makefile modernization
Approved by: oliver@ (as maintainer of various of these ports)
Differential Revision: https://reviews.freebsd.org/D2391
the build failure on FreeBSD 8 (and probably 9), the application
fails to start because the base version of libstdc++ is loaded at
runtime, which does not satify the requirements of webkit-gtk3. The
reason is that evolution does not directly link to libstdc++, so
the rpath added to it by USES=compiler:c++11-lib has no effect. The
first shared library that links to libstdc++ belongs to
evolution-data-server, which does not have USES=compiler:c++11-lib,
which causes the base version of libstdc++ to be loaded.
Unconditionally add USES=compiler:c++11-lib to
databases/evolution-data-server. Adding the rpath to its shared
libraries will cause the newer version of libstdc++ to be loaded
when evolution starts and fix the runtime error on FreeBSD 8 and
9. For standard versions of FreeBSD 10 and higher on amd64 and
i386, it is a no-op, so there is no harm in doing this. If FreeBSD
10 or higher is configured to build with base gcc and clang is not
present, which is an option on amd64 and i386 and is mandatory on
some tier 2 platforms that don't have clang support, then
USES=compiler:c++11-lib is needed.
PR: 199746
Differential Revision: https://reviews.freebsd.org/D2388
Reviewed by: kwm
Approved by: mat (mentor)
MFH: 2015Q2
When using GH_TAGNAME the DISTNAME would have GH_PROJECT and GH_ACCOUNT in
it. When not using GH_TAGNAME it would not have this. Now both cases
will add in the GH_PROJECT and GH_ACCOUNT.
Add special care to ensure that the DISTVERSION is not added in twice. If
a port does GH_TAGNAME=v${PORTVERSION} it will be added in twice though. For
that case DISTVERSIONPREFIX=v should be set and no GH_TAGNAME should be used.
empty() is used rather than (!defined || !${}) to support fmake.
The purpose of setting DISTNAME at all in these cases is to make it more clear
that the distfile is from *GITHUB* and to avoid collisions if a project were
to be renamed or moved. Without adding in GH_PROJECT and GH_ACCOUNT then there
are real risks that collisions on filenames would happen on renamed or moved
projects, which is fairly common. A GITHUB-generated file may not match
a custom-rolled or git-archive-rolled distfile.
PR: 199069
With hat: portmgr
Testing done: All USE_GITHUB ports without GH_COMMIT were checksum/fetch/extract/WRKSRC tested.
