> Patching for this is not sustainable, moving to 2.x makes a lot more > sense. What I don't know is whether it makes sense to do that in ports > or to take the approach we took for a lot of other PHP-based web apps > previously removed - if it needs patching to work on OpenBSD anyway > then I think it does make sense to keep as a port - if it can just be > used directly with normal upstream instructions then possibly not. > > btw see net/librenms "make dist" for another port that uses vendored > laravel, etc (also an example of something which _does_ need patching > for OpenBSD, e.g. we don't have whereis -b, and some paths need > changing). >
Hi Stuart, In that case I think we can remove this port. Following the upstream instructions to build from source worked without any modifications for OpenBSD. I tested it with OpenLDAP (ldapd(8) will not work as it does not allow querying for the schema) without issue. I had planned to port other software I use like Firefly III and Dolibarr which are also Laravel-based apps but they similarly do not need any OpenBSD specific changes. I will say though it is helpful to have a README that walks through database setup, httpd setup, etc. We would be losing these types of things. Most upstream instructions usually just focus on Apache and Nginx for setup. I'll hold them in my tree if thoughts around this change. Cheers -- Chaz
