Thanks. I've decided to try to compile it through the ports packaging system, which turned out to be a rabbit hole: 3.2 uses meson as the build system, and it's been quite the learning curve to sort out the dependencies and get it to build cleanly. It's almost there, for some undefinable value of "almost" and "there".
The main query I have at the moment is that it looks for krb5-gssapi as part of the build process. I can get that easily enough with heimdal, but the question is whether it would be desirable to build it without that library or not. (It's used for GSS-TSIG on dynamic DNS updates). For testing purposes it doesn't matter, but it could be important for some use cases. Leaning towards having separate flavours: one bare bones; one each for PostgreSQL and MySQL; and two variants of all three - with and without GSS-TSIG. (acknowledging that there have been issues with the PostgreSQL support in the past and that it was turned off once boost 1.87+ was packaged, so that might end up being another rabbit hole.) General comments and advice on this would be welcome. (If you're going to do something, do it properly...) As a side note, I have the updated port for log4cplus working; in light of Stuart H's comment about it being held back because of Kea, I'm not going to submit the diff to this channel until I have an updated Kea operational as well. (Feel free to ask me for that diff if you want it. I just don't want confusion about whether it should be updated or not until the blocker has been properly resolved.) Thanks again. On Mon, Sep 7, 2026, at 18:57, Stuart Henderson wrote: > On 2026/09/07 09:49, Stuart Lamble wrote: >> Bump - does anybody have any comments or suggestions? > > don't remember full details but check that logging works and it doesn't > hang at shutdown/restart - had issues with one or other of those with > kea when I've tried updating log4cplus previously (it was specifically > kea that was holding it back)
