On Wed, 2006-06-21 at 14:39 -0500, Eric Boutilier wrote: > On Tue, 20 Jun 2006, Laszlo (Laca) Peter wrote: > > > > ... > > That said, it's possible that files do not get build due to build > > issues, so it's a good idea to combine automatically generated > > pkgmaps with reports that find the differences... > > Can you elaborate? It's not clear (to me anyway) what you mean by "reports > that find the differences". I read the message you just posted too...
I was originally thinking about some scripts that run diffs between pkgmaps, in fact I think Brian Cameron already has something like that which he uses for preparing ARC materials. But it's even simpler than that: the plan is to add *.proto [1] to spec-files/prototype/sparc and spec-files/prototype/x86 Then, after each milestone build release engineering will cp the new proto files from /jds/packages/PKGMAPS/proto [1] to spec-files/prototype/<ARCH> and run svn diff to see what changed.[2] If the changes are valid (expected) then commit the new spec files. If not, it's equivalent to the SFW or CCD build breaking and we obviously need to go and find out what went wrong. Laca [1] prototype files generated by pkgbuild [2] the prototype files are sorted so only real changes will be found
