On Thu, Feb 22, 2007 at 10:55:28AM +0100, Richard Guenther wrote: > Yes - I did this once semi-manually by ensuring the built packages is > (nearly) bit-for-bit identical to the old one. I hope to get back to it > at the point OBS supports bootstrapping Base:build.
That functionality would definitely be useful for other purposes as well. I implemented result comparison for a different packaging system to drastically reduce workload of the build system. Having this feature one doesn't have to trigger the full transitive closure of all dependent packages if one of the root packages is changed but only the packages that directly depend on the changed package. In the next step only those packages rebuilt will trigger packages depending on them if the rebuild actually resulted in a change. For example if you change a package like bison and bison is used to build a tool that is used to build many other packages then without this a change to bison will trigger a rebuild of all packages depending on the other tool. If the check is implemented and the other tool does not change due to the bison change a huge number of packages can be just safely ignored on rebuilding. This does not only save much CPU power for building but can also reduce the number of versions of a package because you never keep packages with identical content. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:[EMAIL PROTECTED] "Quidquid latine dictum sit, altum sonatur."
pgpsLWAOBxZ7a.pgp
Description: PGP signature
