OK landry@
upstream hardcodes directories with dictionaries,
we rely on mozilla-dicts - including a patch
to look for dictionaries in that directory.
Patch submitted upstream as:
https://github.com/wereturtle/ghostwriter/pull/285
- termlib and ncurses are now both "soname curses" from bsd.lib.mk 1.92,
rename and shift into common WANTLIB block, similar to Bjorn's diff
- use SEPARATE_BUILD, from Bjorn
ok bentley@
OpenJK is an effort by the JACoders group to maintain and improve the
game engines on which the Jedi Academy (JA) and Jedi Outcast (JO) games
run on, while maintaining full backwards compatibility with the
existing games. This project does not attempt to rebalance or otherwise
modify core gameplay.
Our aims are to:
* Improve the stability of the engine by fixing bugs and improving
performance.
* Provide a clean base from which new JO and JA code modifications can
be made.
Also sync pkg/README with reality, add daemon_timeout=120 to the rc.d
script (since Snort can take a while to start with the current rules),
and update/regenerate patches.
#1422203 & #749312, and it's doubtful this will change even if i'm
trying to discuss it in #1432591. Instead, a README is provided with the
corresponding commit hash with which we're supposed to hammer
hg.mozilla.org, with varying success in terms of speed. Normally, it
shouldnt be the case for real releases..
Add the necessary plumbing to set DISTFILES/DISTNAME/MASTER_SITES
accordingly if MOZILLA_COMMIT and MOZILLA_BRANCH are set in the consumer
Makefile.
(which is the default for now)
In 59 the possibility to build with system cairo is going away (cf
#1432751) and this hasn't been a "supported" configuration for a while
(numerous weird rendering issues & build failures reported/fixed by
downstreams over the years).
The local cairo copy in gfx/cairo/cairo derives from 1.10. Bug #739096
tracks the eventual update of this copy, which will probably not happen.
Catch2 stands for C++ Automated Test Cases in a Header and is a multi-paradigm
test framework for C++ which also supports Objective-C (and maybe C). It is
primarily distributed as a single header file, although certain extensions may
require additional headers.
ok jca@ Thanks!
Setting DEBUG changed the cmake build type ("release" vs "debug"), which
had a bunch of undocumented and surprising consequences:
- changing CFLAGS/LDFLAGS etc, potentially to values unsupported on
OpenBSD, instead of just using what the user passed in DEBUG
- PLIST changes which break packaging when using PLIST_DB (default)
Leave DEBUG alone and introduce MODCMAKE_DEBUG as a documented feature
instead, as proposed by various folks. Reluctant ok landry@ (thanks!)
