The PR 289853 regarding updating net/OpenBGPd8 to the last minor
release of the branch has been stale for over 4 months now.
Version 9 has been released at 30-12-2025 and I created PR 292055 the
same day, after verifying this version builds, installs and runs fine
and is yet another smooth drop-in-upgrade.
Regarding the 'new port for each major release' practice:
As I wrote in PR 292055, IIRC this stems from a major release that
introduced breaking changes in the config syntax. Since the syntax has
been considered stable for many versions now, we might want to drop
that practice and move to a 'net/OpenBGPd' port that always holds the
latest release - which is the only one supported by upstream anyways.
At the very least we should deprecate/remove the ancient releases 5-7
(ASAP).
@Kurt Jaeger: I see that you are quite busy and involved in a lot of
PRs. (Again: Thanks for all the work!)
We are an active user of OpenBGPd (currently on 11 hosts in production;
6 FreeBSD + 5 OpenBSD) and I could spare some time @work to keep the
port updated and test patches and new releases (I'm already doing that
in our build environment anyways). So I'm open to taking maintainership
for OpenBGPd if this is helpful.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 59 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 00:01:57 |
| Calls: | 812 |
| Calls today: | 2 |
| Files: | 1,287 |
| D/L today: |
20 files (23,248K bytes) |
| Messages: | 210,076 |