* On 2018-05-21 at 17:17 BST, Jason Bacon wrote:
On 05/21/18 10:49, Jonathan Perkin wrote:
* On 2018-05-21 at 16:44 BST, Jason Bacon wrote:
I'm trying, for the first time, to run a full bulk build following a major
cvs update. Until now, I've built everything
from a fresh tree. This time I'm rebuilding -current and there have been
some core updates since the last build.
I'm wondering if there's a canonical way to deal with the situation where
there has been an upgrade to something
that's already in the bootstrap kit. I can figure out how to get around it
manually, but before I do that, is there
a simple setting in pbulk.conf or something like that? I'm not seeing
anything in the docs or anything that sticks
out in pbulk.conf, but maybe I'm just overlooking it.
There's no feature in pbulk to do this. In our trunk builds I just
perform a new bootstrap for every build, it only takes a few minutes.
Creating a new bootstrap doesn't change whether pbulk will rebuild a
package or not, that will always happen if a package or its
dependencies have been touched since the last build.
Thanks, Jonathan and Sevan.
Does it look at timestamps on the source tree, package versions in
packages/All, both, something else?
The logic is implemented here:
https://github.com/NetBSD/pkgsrc/blob/trunk/pkgtools/pbulk/files/pbulk/scripts/pkg-up-to-date
and primarily uses the build version (pkg_info -b) information. If
any of that information changes (files added, removed, or $NetBSD$
changes) the package is rebuilt.
If any package is rebuilt due to the above, then any package that
depends on it (for either build time or run time) is also rebuilt, and
this is performed recursively, so for example a change to cwrappers
will result in pretty much every single package being rebuilt.