From: Thomas Frohwein <tfrohwein@fastmail.com>
Subject: Re: Update Kakoune to 2026.04.12
To: Lydia Sobot <chilledfrogs@disroot.org>
Cc: Solène Rapenne <solene@openbsd.org>, ports@openbsd.org
Date: Fri, 17 Apr 2026 14:43:47 -0700

On Thu, 16 Apr 2026 06:23:21 +0200
Lydia Sobot <chilledfrogs@disroot.org> wrote:

> >I've used it on amd64; here all tests pass.  
> Interesting
> >Would you be interested in
> >taking Maintainer, as Solene has been otherwise occupied recently?  
> Sure

That's awesome, thanks! Feel free to reach out with issues/questions. I
have an interest in keeping kakoune working, as I use it frequently
myself.

I committed it with you as maintainer. Also added the adjustments from
`make update-patches` and `make update-plist`.

There are a few things that I recommend checking routinely when
updating a port:

- make update-patches
- make update-plist
- make test
- make port-lib-depends-check
- I generally also run portcheck(1) once
- if the port has SHARED_LIBS (grep -i shared Makefile*), then check
  for API changes (e.g. with /usr/src/lib/check_sym)

It's also often worth taking a look at the build log for which flags
are used (sometimes an `-O3` or other undesired flags find their way
in) and close reading of the `make configure` stage of the build
process.

`make update-patches` can often just fix where patch(1) needs to fuzz
to apply. `make update-plist` is pretty crucial to at least check...
without that, additional files installed by the project will not be
installed (because only what's in pkg/PLIST will end up on the system).
Sometimes that's minor, sometimes it breaks the port in a variety of
ways. You can use `diff -u pkg/PLIST{.orig,}` to see what's changed.

Not comprehensive, but maybe helpful for some future ports work :]