On Mon, 16 May 2011 18:24, Greg Freemyer <greg.freemyer@...> wrote:
On Mon, May 16, 2011 at 7:25 AM, Vincent Untz <vuntz@opensuse.org> wrote:
Hi,
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
Brainstorm only:
Can you have glib depend on an older version of pkg-config that still has its own glib?
That sort of "fix" might even last for years before glib depends on new pkg-config functionality.
Still not a very clean way to do things, since you need both the old static pkg-config package in factory as well as the new one.
Greg
Food for tought: - How do they build pkg-config upstream? - Don't they have the same trouble? None the less, could a static glib for pkg-config be the temporal answer for us? - at least until upstream has a solution?
From a user of pkg-config point-of-view, what are the advantages of version 0.26 versus the prior version?
Is 0.26 really needed? - or would a (error) patched prior version still suit or needs? Thanks, Yamaban out. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org