hashashin at gmail.com
Mon Oct 23 00:34:53 PDT 2006
On 10/23/06, Daniel Macks <dmacks at netspace.org> wrote:
> We need to have "GLIB" displayed so that if it fails, one knows that
> it's GLIB_CFLAGS and GLIB_LDFLAGS that need to be overloaded from the
> environment. IMO, *if* the check succeeds, do people really care that
> much which specific requirements were checked? OTOH, if the check
> fails, then one really *does* need that info in order to figure out
> what needs to be installed.
I think it is a matter of coherence. The truth is that you may use
GLIB as your variable, but you can use whatever you want. Thus, if I
use XPTO would you know what CFLAGS and LDFLAGS to define? I
understand that the variable might be important, but it doesn't have a
meaning. In the other hand, if the test fails and prints the missing
packages then you will know what XPTO means. But then, we can always
make the variable to be print if the test fails.
Anyway, if you all prefer it as it is, please change the string from
"checking for GLIB" to something else, like, "defining GLIB variables"
as nobody guarantees that the variable name is a package.
Sorry abuot the rant :)
More information about the pkg-config