On Mon, May 16, 2011 at 05:58:09PM +0100, Tejas Guruswamy wrote:
On 16/05/11 12:25, Vincent Untz wrote:
pkg-config 0.26 is out and one of the changes is the removal of an internal copy of the glib code. That means that pkg-config now requires glib to build. However, glib requires pkg-config to build. Hence a fun build loop.
Does anyone have any idea how we should deal with this situation?
Thanks,
Vincent
Surely the OBS can deal with build loops by simply using the last successful build of a package?
Yes, of course. But see below.
I'm sure there are other build loops in the distribution ...
A build loop has two big disadvantages: - it increases build time, as the packages have to be built twice - it makes a bootstrap much harder, e.g. when there's an incompatible change or the soname of a library changes. So, the rule of thumb is: avoid cycles if possible. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org