stefan.seefeld at gmail.com
Mon Apr 2 12:09:44 PDT 2012
a small question / suggestion from the back row...
I understand that pkgconfig needs support code that is already invented
multiple times in various runtime libraries, and I also understand that
dragging in such dependencies for a fundamental tool such as pkgconfig
is very inconvenient for many.
What speaks against bundling one of those prerequisite runtimes (or the
required subset) with pkgconfig ? In other words, couldn't you just set
up a local "vendor branch" from glib and compile that right into
pkgconfig, just to break out of the dependency loop ?
Has that already been considered ?
...ich hab' noch einen Koffer in Berlin...
More information about the pkg-config