net-im/nheko 0.12.1_4 FreeBSD

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 …

Qt 6.11.2 edition. These ports are known to directly use or link to a library that uses the Qt private API and must be rebuilt with every Qt update. Qt *public* API/ABI compatability is excellent, so most consumers don't need to necessarily be rebuilt between patch or even minor releases, but use of the private API breaks this compatibility between even patch releases and its use is highly discouraged. This list [1] is based on histortical data. We don't have time to revisit every port on the list with each Qt update, so if your port has dropped Qt private headers and was bumped in error, please remove it yourself if you have write access to the Wiki or alert someone on kde@. [1] https://wiki.freebsd.org/KDE/Qt MFH: 2026Q3

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 …