On Tue, 17 Jul 2012 17:03:07 +0200
Juergen Weigert
On Jul 17, 12 11:37:57 -0300, Claudio Freire wrote:
If a package builds differently in different environments, it's bad for stability to actually build it in different environments. You want to be sure you'll build it the same way each time, so you know you're not introducing bugs by simply rebuilding.
For asserting a particular environment, we need to do two thing: a) make sure everything is there that should be there. b) make sure nothing is there that should not.
BuildConflicts appears to be the tool to keep packages out. While BuildRequires is quite practical for a), BuildConflicts appears to be not so helpful for b). It would require a patient maintainer to find all possible conflicts.
How about this: - with each successful build, record the list of packages that were in the buildroot - with all builds, report added and removed packages compared to the last recorded list.
While this alone does not enforce reproducability, it documents a way towards reproducability, by pointing out changes in the environment.
cheers, JW-
Hi That's always there in the build log from start to finish... -- Cheers Malcolm °¿° (Linux Counter #276890) SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.34-0.7-default up 7 days 14:33, 4 users, load average: 0.32, 0.20, 0.22 CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org