On Saturday 24 October 2009 03:58:17 Murray S. Kucherawy wrote:
> Looks like there's mostly negative views of the idea of using pkg-config
> with autoconf at least over there:
>
> The root of the thread, if you're interested:
> http://lists.gnu.org/archive/html/autoconf/2009-10/msg00132.html >
not true in the way I understood this. aclocal installs the PKG_* macros in
aclocal.m4. If you run aclocal on a machine without the PKG_* m4 original
files on I'm not sure what happens.
summary - may affect some users that what to rebuild the autoconf of this
package on non- pkg-config installed systems.
generally considered a good thing. If we need to check features we do what we
did with openssl - let pkg-config find the library and then AC_CHECK_* the
librarys/includes more carefully
As a) is caused by someone either knowledgable or silly I don't think we need
to worry here.
b) is actually how I tested the libopendkim development without clobbering
system files and gives users flexibility of version selection a level before
resorting to {NAME}*FLAGS settings
This is quite true. Library CFLAGS are populated to the opendkim build. The
ones that are populated will be the openssl/tre libs. By default these don't
polute too much. Distro maintainers sometimes make sure these are fairly
clean. If the user compiles them then they get a bit more confusion if they
compile openssl for example with CFLAGS that they don't want in opendkim.