Bryan Drewery

#1260 covers make jobserver support, which isn't a job scheduler, but will come into play here somehow to be numa-aware.

https://pastebin.com/sNvmU3DH ``` [53/240] Deinstalling FreeBSD-utilities-dev-15.snap20250807020358... [53/240] Deleting files for FreeBSD-utilities-dev-15.snap20250807020358: 100% [54/240] Deinstalling FreeBSD-utilities-lib32-15.snap20250807020358... [54/240] Deleting files for FreeBSD-utilities-lib32-15.snap20250807020358: 100% [55/240] Deinstalling FreeBSD-utilities-man-15.snap20250807020358... [55/240] Deleting files for FreeBSD-utilities-man-15.snap20250807020358: 100% [56/240]...

Setting it to the tree commit timestamp would mean build 2 would have new timestamps for every package wouldn't it? I assume this would need per-port commit timestamps. That's quite...

I closed your other PR #1228 in lieu of #1271. #1271 will supersede this PR too as it will use the set `PACKAGE_FETCH_URL` as the repository to pull from. I...

This should be fixed by the new incremental build. It's off-by-default because it can cause some surprising behavior, and I need to do some writeups on it to make it...

> > This should be fixed by the new incremental build. It's off-by-default because it can cause some surprising behavior, and I need to do some writeups on it to...

> > This should be fixed by the new incremental build. It's off-by-default because it can cause some surprising behavior, and I need to do some writeups on it to...

So, coming back to this issue, it feels like a Discussion. Can I convert it to that?

I'm not sure about this one. `pkg` owns `ABI_FILE` but it doesn't own `OSVERSION`. `OSVERSION` is used by ports.

@bapt how should we make this warning go away? The variables are different purposes, why is `pkg` warning about it?