Forks between the BSD pfs are growing larger as OpenBSD changes their implementations grow and others stay iut of sync. There should be a project, if not to unify pf, but to keep it consistent by attempting to merge changes between the projects as appropriate.
There is such a project. It’s called… FreeBSD. For serious.
From the OpenBSD perspective, even if he did the work, henning can’t force diffs into FreeBSD. Neither is he much interested in stopping development until FreeBSD catches up.
Several parts of the OpenBSD tree which are primarily developed on OpenBSD contain portability affordances that aren’t strictly necessary on OpenBSD, but which assist downstream consumers of that code. The important thing is that those downstream consumers take a somewhat active interest in the code.
Forks between the BSD pfs are growing larger as OpenBSD changes their implementations grow and others stay iut of sync. There should be a project, if not to unify pf, but to keep it consistent by attempting to merge changes between the projects as appropriate.
There is such a project. It’s called… FreeBSD. For serious.
From the OpenBSD perspective, even if he did the work, henning can’t force diffs into FreeBSD. Neither is he much interested in stopping development until FreeBSD catches up.
Several parts of the OpenBSD tree which are primarily developed on OpenBSD contain portability affordances that aren’t strictly necessary on OpenBSD, but which assist downstream consumers of that code. The important thing is that those downstream consumers take a somewhat active interest in the code.