Predrag Ivanovic wrote:
On Mon, 16 May 2011 19:19:06 +0200 Juergen Daubert wrote:
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?
Since glib depends only on core/libpcre, and most ports from opt/contrib are likely to depend on pkg-config, cleanest/simplest solution would be moving glib to core, imho. btw, are ports from core considered implicit dependencies (should not be listed in Depends field in Pkgfile since it is assumed that there are always installed on a system)?Or are there exceptions to that?
thanks and best regards Juergen
Pedja _______________________________________________ crux-devel mailing list crux-devel@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux-devel
As far as I know you do not list any gcc/glibc and friends considered as the tool chain, but you do list ports in core that you link to not things like perl that's not being linked to. say your port foo links to glibc, zlib, perl you only list zlib. Regards, Danny Rawlins <Romster>