sysutils/cfengine-devel3.28.20260920_1,1

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

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

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
release, pinned to the 0.x branch with PORTSCOUT=limit:^0. and mutually
conflicting with databases/lmdb, which retains 1.0. The two packages
cannot be installed simultaneously, but having lmdb0 available means:

* Ports known to require the 0.9 ABI can declare an explicit dependency
  on databases/lmdb0 until they are validated against 1.0.
* Users with existing databases in the 0.9 format can still access the
  mdb_dump and mdb_load utilities to migrate data before upgrading.
* The package conflict prevents accidental mixing.

All 50 direct dependents of databases/lmdb are redirected to
databases/lmdb0 for now with a PORTREVISION bump, effectively restoring
the tree to the state prior to the LMDB 1.0 update. Once all dependent
ports are validated against LMDB 1.0, they will be moved back to
databases/lmdb and databases/lmdb0 will be removed.

PR:             ports/296530

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Fix distfile

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

libxml2: chase libxml soversion bump

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine*:	Fix configure

cfengine325 and -devel now depend on librsync.

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine*-devel: Fix port version

Add PORTEPOCH to avoid port version going backwards.

Fixes:		00e1cb3fc3bd

sysutils/cfengine-devel: Update to latest GH commit

Also adjust the date and version to conform to standard.

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

databases/mysql57-*: Remove expired port

*/*: 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)

sysutils/cfengine-devel: Include missing patches

Include patches missed in c3e20983b789.

Fixes:		c3e20983b789

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit

sysutils/cfengine-devel: Update to latest GH commit