Matthew Seaman <matt...@freebsd.org> writes: > poudriere only knows that the dependency changed. In effect, to find > out if the package of interest would be changed because of that, it has > no other recourse than to build the package. Now, if you can come up > with some heuristics whereby you can examine the changes to a port and > determine that they will not cause significant downstream changes, and > do that reliably and faster than just rebuilding the package, then I'm > sure the poudriere developers would be eager to incorporate them. > > Failing that, poudriere re-building everything that might be affected is > the sensible choice.
If I know that only the actually changed ports need to be rebuilt, I go into my jail but instead of running poudriere, I use "portmaster -g". Unfortunately, it's really easy to be wrong about "knowing" that. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
