On 2025/07/11 15:59, Sergey A. Osokin wrote: > On Fri, Jul 11, 2025 at 08:41:57AM -0700, Jeremy Evans wrote: > > On 07/11 03:34, Sergey A. Osokin wrote: > > [...] > > > > I do believe that the passenger sub-port can be decoupled from the nginx > > > port like it's set in FreeBSD ports tree. Also, passenger needs to be > > > updated to the recent version, 6.0.27, that works well with the recent > > > version of llvm on FreeBSD. > > > > Apologies, but I couldn't tell from your response whether you were using > > the nginx passenger subpackage and cannot switch to puma. Can you clarify? > > Personaly, I'm not using nginx passenger sub-package, however it's > better to see several different ways to play a code, rather than stick on > a specific solution. That's not only for today, but a sort of an investment > for the future needs.
We take a slightly different approach in OpenBSD ports compared to FreeBSD - if something is adding maintenance burden and isn't actually being used, especially if there is a more maintained alternative, we'd often prefer to remove it. If someone shows up who uses it and wants to help out then perhaps it's worth keeping, but otherwise the fact that the port is currently at 6.0.18 (June 2023) and doesn't get mentioned on ports@ often suggests that it's probably not actively used. (We can always re-add later if a maintainer shows up).
