> Am 29.11.2024 um 14:20 schrieb Stuart Henderson <s...@spacehopper.org>: > > On 2024/11/29 01:19, Mike Fischer wrote: >> Thanks for that very thorough explanation Stuart! >> >> And waiting for 7.7 to get PHP 8.4 is fine in this context. I had >> thought that there was less work involved with backporting. PECL is >> not a requirement for what we are using I think. But some of the PHP >> extensions are. > > The PHP extensions themselves are fine with this approach.
ok. > /usr/src and /usr/obj are normally just used for building the > base OS. The size requirements for this should fairly static (for each architecture and OpenBSD release). So based on the default partitioning scheme what would be the minimum/recommended size of the disk that supports building the base OS (for me amd64 or arm64 are most interesting)? 20 GB? 30 GB? 40 GB? …? > If building ports, I would strongly recommend a separate filesystem > for /usr/ports. > > For something like this I would have thought around 30GB would be > enough - more would be needed for some of the larger ports or if > you're building a wider variety of things (unless you split things > up further, this includes the build directory aka "pobj", built > packages, distfiles, etc). The filesystem holding the build dir > should be mounted with the "wxallowed" flag. > > /usr/local also needs to be large enough to install the dependencies > you need to build things - I usually go with 20GB for this though > you might get away with less. That is very helpful information. Thanks! >> But if building my own ports is the way to get PHP 8.4 on -stable then >> for this purpose it might be easier to bite the bullet and install a >> -current VM and set it up to enable the web services. At least for >> that stuff I know what I’m doing ;-) > > That probably would be simpler - package snapshots now include 8.4 so > nothing to build yourself. Depends whether you think building things > from ports would be a useful thing to learn really. (OTOH if you're > doing it by hand at the moment, it might be better use of time to note > the steps needed to setup the web environment and script it :-) I think I’ll treat the building of ports as a separate project. Definitely interesting and something I’d like to eventually be able to do, but more of a hobby right now. As for scripting the machine setup, yes I’d love to be able to do that. I do have documentation, even a step-by-step guide on setting up a new machine. But many steps still seem easier to do manually. There are also external things involved, such as IPs, DNS, external firewalls, etc. Those would be hard to include in any automated scripts. Depending on where I host the test machine I might also need to deal with dynamic public IPs. Thanks again! Mike
