On Tue, 17 May 2011 16:03, Stephan Kulow <coolo@...> wrote:
Am Dienstag, 17. Mai 2011 schrieb Dimstar / Dominique Leuenberger:
On Tue, 2011-05-17 at 14:35 +0200, Stephan Kulow wrote:
You can only break artificial loops. This one is real. When bootstrapping you have to have both, so it's real.
I only see two solutions (both are ugly): * Merge the Sources into one package and have pkg-config build as subpackage
from glib (or the other way around)
* avoid pkg-config in glib
Avoiding pkg-config in glib2 is not really difficult. It checks for only 4 things using pkg-config:
Hmm, after checking: pkg-config is already in the basic bootstrap cycle. So if pkg-config uses glib, glib will be in that cycle anyway. So there is no point in avoid pkg-config in glib.
I wouldn't say that. Either you a) include a striped down / older version of glib in pkg-config source (like the 0.25 version does, no need for glib package in bootstrap), b) make the build of glib independent of pkg-config, to avoid any loops in the bootstrap cycle. This saves time, nerves, and other resources. For both of these solutions, examples / todos where already done in this thread. What remains is to find out if either of these solutions are good enough, or if there is more research needed to decide what to do. No matter how we decide, until we force pkg-config>=0.26 into factory, we have the time to find a working way to resolve this, or it WILL come back to bite us in our behinds, "hello Murphy" on this. Yamaban out. PS: I do not have the expertise do say this or that solution is better, but doing an ostrich doesn't help us any. And yes, bootstraping is ugly. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org