This comes from a new upstream, that focused on moving fwbuilder from
Qt4 to Qt5. There is no other functional changes to be expected by this
update.
OK rsadowski@
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
libfwbuilder got merged into fwbuilder.
Besides still not fully supporting all new features of recent OpenBSD pf,
it generally works well.
feedback and OK sthen@
handle a few appliances, and PF.
Having this around may help some people start up on OpenBSD (yeah, right)
and it also comes with a few reasonable policies.
Nice things:
- the produced files look decent for mechanically generated files.
- fwbuilder can take advantage of packet-filter specific features.
For instance, it knows about modulate state, or can tweak the parameters
for state keeping on pf.
