On Wed, May 18, 2011 at 10:19:14AM +0200, Michal Soltys wrote: Hello Michal,
W dniu 16.05.2011 19:19, Juergen Daubert pisze:
Hi all,
the latest pkg-config, version 0.26, no longer ships with a bundled glib but depends on a system glib. That means core/pkg-config would depend on opt/glib, which is of course not acceptable.
We have two options IMO:
a) move pkg-config to opt. At a first glance I don't see any core-port depending on it, so this should work. The drawback is, that every opt/contrib-ports which has pkg-config as a (buildtime-)dependency must list it in the dependency header. b) move glib to core.
Opinions?
Though I'm not a dev, I'd opt for (b). Apart from pkg-config, at least one more package could depend on glib moved to the core as well (udev).
Thanks for your contribution, even if you are not (yet) a official CRUX maintainer, at least the udev port is your main work ;) What's the benefit if we enable udev options that depends on glib? Do we really need that? Is this a requirement for stuff like gnome?
In such case I'd also add to glib's Pkgfile:
--with-runtime-libdir=../../lib
and probably (though I'm not 100% sure if it's really needed):
--with-gio-module-dir=/lib/gio/modules
and adjust (just install tends to fail with bigger -jN setting):
make -j1 DESTDIR=$PKG install
This is healthier for specific apps that require ->udev->glib to work properly before /usr is mounted (for those that mount /usr separately). E.g.:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commit;h=18f5c802dfd958d9a...
Hmm, if udev depends on glib, wouldn't it be better to install the required glib libraries into /lib instead of /usr/lib? Greetings Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux