poudriere: reduce the number of rebuilt packages?

[Matthew Seaman]

On 12/01/2015 21:05, Karel Miklav wrote:
> On 12.01.2015 18:55, Mathieu Arnold wrote:
>> > Well, no, there is not, and unless you figure out an algorithm to do it,
>> > and I'm saying algorithm in the mathematical sense, not heuristic, that is,
>> > one that is always right, feel free to submit a patch for it :-)
>> > Now, there's a good chance that it will be slower than rebuilding all the
>> > dependencies.

> What about the logic in pkg, aren't both programs solving the same problem?

No, the problems solved by pkg and poudriere are very different.  pkg(8)
has the massive advantage that it already has access to the built
packages, including analysis of the dynamic linkage of all the binaries
included there.  That makes it relatively simple for pkg to work out if
a change in some dependency has had a material effect on the package
being considered.

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.

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 971 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20150113/b65c1030/attachment.sig>