Mailinglist Archive: opensuse-packaging (140 mails)

< Previous Next >
Re: [opensuse-packaging] Breaking the loop with pkg-config 0.26
Le jeudi 12 janvier 2012, à 09:05 +0100, Ludwig Nussel a écrit :
Vincent Untz wrote:
[...]
The issue here is that to fix the loop, we'd need to eradicate the
pkg-config dependency on everything that is below glib2. This includes
at least libffi-devel, libselinux-devel, pcre-devel and zlib-devel. And
libraries that might be below those.

This sounds annoying, as it's easy to re-introduce a build loop. On the
other hand, I don't really see what else we can do.

Would it be possible to build a special, minimal bootstrap glib that
is only used for building pkg-config?
A trick like that is used by other packages too (krb5-mini,
ghostscript-mini, etc ...).

Unfortunately, glib2 has hard dependencies on zlib and libffi, so as
long as the devel packages for those bring pkg-config in, it's not
possible.

For reference, this is what depends on pkg-config in a glib2 build root:

pkg-config is needed by (installed) libsepol-devel-2.0.41-14.19.i586
/usr/bin/pkg-config is needed by (installed) libbz2-devel-1.0.6-16.6.i586
/usr/bin/pkg-config is needed by (installed) udev-173-7.1.i586
/usr/bin/pkg-config is needed by (installed) pcre-devel-8.20-2.2.i586
/usr/bin/pkg-config is needed by (installed)
zlib-devel-1.2.5.2_git201109121534-19.1.i586
/usr/bin/pkg-config is needed by (installed)
libffi46-devel-4.6.2_20111212-1.1.i586
/usr/bin/pkg-config is needed by (installed) libsepol-devel-2.0.41-14.19.i586
/usr/bin/pkg-config is needed by (installed) libselinux-devel-2.0.91-17.13.i586

We can remove the deps on libselinux-devel, libsepol-devel and
pcre-devel. As to libbz2-devel and udev, I think they're part of the
packages that get installed in all build roots -- but we can at least
fix udev by moving the .pc file to a devel subpackage.

Cheers,

Vincent

--
Les gens heureux ne sont pas pressés.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >