On 6/30/06, Tollef Fog Heen <[EMAIL PROTECTED]> wrote:
| 4. Custom config tools can often provide more info than available in
| pkg-config (plugin or config directories).
Like:
: [EMAIL PROTECTED] ~ > pkg-config --variable=system_bus_default_address dbus-1
unix:path=/var/run/dbus/system_bus_socket
Sure, but to take an example, PostgreSQL has had pg_config for ages
and other projects use this to get the necessary parameters to compile
against the installed version. There is no way pkg-config can copy the
current set of command line arguments, so you have a backward
compatability issue. Also, what you suggest is not exactly shorter.
It is also used to compile contrib modules that are included in the
distribution. If you started using pkg-config you'd have introduced a
build dependancy on a GPL'd program in a BSD licenced package, not
exactly a good idea.
pkg-config is nice for the constellation of GPL'd libraries currently
installed on most linux systems, but once you step outside of that
it's not quite as useful.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
