pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: bob v0.9.0: dynamic scheduler, history, and lots more



* On 2026-03-27 at 15:16 GMT, Benny Siegert wrote:

On Wed, 25 Mar 2026, Jonathan Perkin wrote:

Just in time for building 2026Q1, I've released the next version of bob. This one includes a big new feature: dynamic MAKE_JOBS and WRKOBJDIR.

This is wonderful, thank you!

I have one pbulk feature that has not made it into bob, I think: setting the output directory for binary packages from the build.

AIUI, when you build with bob, the packages go into /usr/pkgsrc/packages. In pbulk, there is a "packages" variable for setting that directory in pbulk.conf. I have not seen a similar setting in config.lua -- or am I missing a trick there?

The reason I am asking is that I am often running builds with different settings (e.g. with a different default Go version), and I would like to keep them separate. Ideally, I would like the packages to go somewhere under the bob config directory.

For any pkgsrc variables, the one source of truth is mk.conf. Just set PACKAGES in there and that's where packages will be created. That way there is never any conflict between what pkgsrc thinks is set and what the tooling expects.

While you can set arbitrary environment variables using bob, I would not recommend doing so, and I've removed them from the default config files to discourage this as I think it just makes things less reliable.

For example, if you set $packages in pbulk.conf to a different path than what PACKAGES is set to in mk.conf (or the pkgsrc default) then things will break with a cryptic failure. I am trying hard to avoid any such problems.

--
Jonathan Perkin                    pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com


Home | Main Index | Thread Index | Old Index