cfengine-develSystems administration tool for networks
3.28.20261028,1sysutilsΣ=0 3.28.20260920,1Version of this port present on the latest quarterly branch.upstream: 318.7-build1A newer version was found upstream by portscout, first on 2026-10-29.
Cfengine is an automated suite of programs for configuring and
maintaining Unix-like computers. It has been used on computing arrays
of between 1 and 20,000 computers since 1993 by a wide range of
organizations. Cfengine is supported by active research and was the
first autonomic, hands-free management system for Unix-like operating
systems. Cfengine is an autonomic maintenance system not merely a
change management roll-out tool. Cfengine has a history of security
and adaptability.
===> The following configuration options are available for cfengine-devel-3.28.20261028,1:
LIBVIRT=off: Virtualization support via libvirt
MYSQL=off: MySQL database support
PGSQL=off: PostgreSQL database support
===> Use 'make config' to modify these settings
databases/lmdb: allow to install both 0.x and 1.x together
LMDB 1.0 and the legacy 0.9 ABI cannot be mixed, the datanase format are
incompatibles as well.
Rename or relocate everything databases/lmdb0 installs so that it no
longer overlaps with databases/lmdb:
- the utilities are now mdb_copy0, mdb_dump0, mdb_load0 and mdb_stat0
- the header is include/lmdb0/lmdb.h
- the linker name is liblmdb0.so, the shared object keeps its ABI name
liblmdb.so.0 so already linked programs are unaffected
- the pkg-config file is lmdb0.pc
A compatibility prefix holding the previous layout is also installed
under ${PREFIX}/lmdb0/ (include/, lib/ and libdata/pkgconfig/) so that
build systems which expect to find lmdb.h and -llmdb relative to a
single directory only need a path change.
Now all ports should migrate to lmdb 1.X and use the lmdb 0.9 port to ease
in the migration path, lmdb, the lmdb 0.x is supposed to get removed at
some point.
Approved by: mat (portmgr)
Reviewed by: mat
Differential Revision: https://reviews.freebsd.org/D60741
databases/lmdb0: Add port for LMDB 0.9.x legacy ABI
LMDB 1.0 introduced an incompatible on-disk format change and subtle
API breakage: applications that compiled cleanly against 1.0 headers
could fail silently at run time. Known affected ports include dns/knot3,
mail/bogofilter, and mail/postfix; the postfix issue has been confirmed
upstream. Linux distributions such as Arch Linux have observed the same
breakage. Samba can also be affected in certain configurations.
Because the regression is not detectable in an -exp build run -- the
postfix failure only manifests at run time, and bogofilter was caught
only because post-build self-tests happen to exercise this path -- we
cannot rely on package builds to validate the 1.0 upgrade.
This commit introduces databases/lmdb0 as a holding port for the 0.9.35
(Only the first 15 lines of the commit message are shown above )
*/*: Refactor with IGNORE_WITH_MYSQL
- There are multiple ports which has MYSQL options and are non-DEFAULT.
Most of the time committers actually forget to check with the OPTION
enabled and in some cases they are BROKEN with newr versions of mysql.
So test with different versions of mysql and mark IGNOPRE_WITH_MYSQL
appropriately. Due to the EOL of 5.7 this has not been checked.
- Unbreak sysutils/cfengine* with MySQL 8.0 and later
- The primary purpose of running this check is having statistics of the
MySQL usability over MariaDB to explore the future possibility of
shifting to MariaDB as the default as major ports upstream have moved
their codebase to support MariaDB over MySQL.
- The following actions will also be taken after the sunset of MySQL 5.7
If a port is broken on all instances of MySQL/MariaDB:
- If a port has the option of multiple DB backends and MySQL is the
default then the DEFAULT will be changed to PGSQL/SQLITE before
2024Q1. And the OPTION will be removed before 2024Q2. If a
MAINTAINER is aware about such cases and want to prefer PGSQL over
SQLITE or vice versa please do so at your own accord. Otherwise
PGSQL will be preferred over SQLITE.
- If a port has the option of multiple DB backends and MySQL is not
the default then the the OPTION will be removed before 2024Q1.
Approved by: portmgr (blanket)
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
sysutils/cfengine*: Remove skreuzer@ and gjb@ as alternate maintainers
skreuzer@ and gjb@ expressed long ago they were no longer interested
in the cfengine ports. Let's make this official.
textproc/libxml2: bump all LIB_DEPENDS consumers
This is a separate commit to facilitate easier cherry-picking for
quarterly.
PR: 262853, 262940, 262877, 263126
Approved by: fluffy (mentor)
textproc/libxml2: bump all dependencies
This should make sure that all dependent ports will pick
up the new version commited with a13ec21cd733f67a9fc0dc00ab45268bdc236246
Fix CONFLICTS entries of multiple ports
There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.
This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.
Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port
(Only the first 15 lines of the commit message are shown above )
