* On 2024-12-22 at 00:23 GMT, Havard Eidnes wrote:
How, then, about this modification? If /etc/pbulk.conf exists, source it from the default pbulk.conf file? That way, the customizations can be put in a file which is untouched by a pbulk reinstall. (In my case, this happesn in a chroot, of course.)An alternative is something like this: https://github.com/TritonDataCenter/pkgsrc/commit/49e8062b7688935b6c552b5cfc7f67cd7e3c83be which I've been running for over 10 years at this point to support arbitrary builds (and modifications) using the same pbulk build.Hm, do I read that correctly, that you need to remember to pass the config file as an additional optional argument to any of the pbulk commands when starting or restarting the build, so you need to keep the knowledge of that modification "top and center of mind" whenever executing any of those commands?? As such, I think it scores lower on the usability / friendliness scale.
Yes, or set it in the environment.Like I said, works great for me and has supported my vast array of bulk builds over the years, but agree it isn't for everyone, though I'd also argue the same about loading a static file, especially as then you'd need to remember to copy it into every sandbox on every invocation or bad things could silently happen. If you specifically set a command line argument then at least you get an error message if for some reason it doesn't exist in a sandbox.
There aren't really any good options when everything is so fragile. -- Jonathan Perkin pkgsrc.smartos.org Open Source Complete Cloud www.tritondatacenter.com