On 2025/10/18 05:27, Theo Buehler wrote:
> On Fri, Oct 17, 2025 at 08:23:26PM +0000, Purple Rain wrote:
> > Hello ports@ and Damien
> > 
> > Here is a updated port www/forgejo 7.0.16
> > 
> > This works OK on SecBSD and OpenBSD-7.8-current amd64.
> 
> Is there a reason to stick with 7, which is EOL since July 2025?
> I would have expected a port to target 13, or at least 11.

Looking at https://forgejo.org/docs/latest/admin/release-schedule/
I wonder if LTS (currently 11) might align better with our schedule.

The patches to default config seem excessive and easily result in
conflicts for updates.

For starters most of the overridden paths seem to have sane defaults
relative to AppWorkPath so perhaps set that via --work-path in
daemon_flags and use the default paths or relative paths? (if you can
avoid needing SUBST_CMD for patched files, that will also simplify
updating patches). That also avoids missed patches if an update addds a
new configurable path.

I'd tend to avoid patching the .ini for personal preferences and
restrict it to just changes needed for the port, unless really
important. Again to reduce conflicts for updates.