I didn't know about Yocto, but reading through its documentation, it looks far more complex than NetBSD's build.sh. And then, I read:
If the machine you want to use Yocto Project on to build an image (Build Host) is not a native Linux system, you can still perform these steps by using CROss PlatformS (CROPS) and setting up a Poky container.
...
> With CROPS, which leverages Docker Containers, you can create a Yocto Project development environment that is operating system agnostic. You can set up a container in which you can develop using the Yocto Project on a Windows, Mac, or Linux machine.
... which is not close to what NetBSD's build system does, like at all.
As for buildroot: "Buildroot is designed to run on Linux systems." (a "red flag") and the list of host dependencies to install is pretty large, which is also different from NetBSD's build.
Plus Buildroot and "other embedded-oriented systems" are, well, something specifically designed to build embedded system images with Linux, not a "standard" Unix-like OS that happens to have a build system that works well for embedded. A big plus for BSD is its monorepo style of development: customizing and patching the system is trivial. With buildroot, well, you have Linux's hodgepodge style of development, so picking and choosing components is simple, but modifying any of them is hard.
So what NetBSD's build system offers doesn't "seem fairly standard" to me. Definitely not the "run on pretty much any host POSIX platform", which is not common. And when you involve Docker in the picture, I also say that other systems fail the test of "all without root".
Comments
I didn't know about Yocto, but reading through its documentation, it looks far more complex than NetBSD's build.sh. And then, I read:
... which is not close to what NetBSD's build system does, like at all.
As for buildroot: "Buildroot is designed to run on Linux systems." (a "red flag") and the list of host dependencies to install is pretty large, which is also different from NetBSD's build.
Plus Buildroot and "other embedded-oriented systems" are, well, something specifically designed to build embedded system images with Linux, not a "standard" Unix-like OS that happens to have a build system that works well for embedded. A big plus for BSD is its monorepo style of development: customizing and patching the system is trivial. With buildroot, well, you have Linux's hodgepodge style of development, so picking and choosing components is simple, but modifying any of them is hard.
So what NetBSD's build system offers doesn't "seem fairly standard" to me. Definitely not the "run on pretty much any host POSIX platform", which is not common. And when you involve Docker in the picture, I also say that other systems fail the test of "all without root".