On 2024/11/28 22:05, Mike Fischer wrote: > Hi! > > I noticed that a new port for php-8.4.1 was made available for -current. > Thanks for the very prompt implementation the same day it was released! > > Now I was wondering whether a backport of php-8.4.1 to 7.6-stable was planned? > > It would certainly help with getting code adjusted to the 8.4 branch of PHP. > We have a few test-VMs running -current but they are not really set up for > web services like the production machines running 7.6-stable. So using the > latter would be much easier for this.
Hi Mike, I'm not planning to backport the 8.4 dir (it's not something we've done before with PHP, and hooking up the various things around a new PHP version - pecl ports, etc - is a bit too much for -stable). However if you just need PHP itself and not various things from pecl, all the infrastructure for building lang/php/8.4 *is* in place in -stable, so you should be able to build yourself fairly easily if you fetch the relevant bits of the ports tree. If you don't already have a ports tree checkout on a 7.6-stable machine, see the faq for info on fetching it, and make sure you "cvs up -r OPENBSD_7_6" across the whole tree to make sure that you have everything - you will need to use cvs rather than the git conversion (it's proven impossible to get a working continuously updated git conversion of the OpenBSD CVS trees unless tags/branches are ignored). That could be one of the existing web machines, or e.g. a fresh VM to build on, and just copy packages across. With the 7.6-stable tree in place, you should be able to easily copy the lang/php/8.4 directory from a -current machine (or indeed as CVS does not require a checkout to be consistent across the tree, you can fetch most of the ports tree with the OPENBSD_7_6 tag, and get just that dir from -current: cd /usr/ports/lang/php; cvs up -PdA 8.4). Then build the port as normal (there will be quite a few dependencies for the optional subpackages; "make prepare FETCH_PACKAGES=" will save a lot of time and pain by downloading the relevant packages rather thann building them locally). It's not impossible to build pecl things there too but I think if you need to go further than the above you're probably better off building out a testbed on -current as the work needed on the ports tree is a lot more spread out.
