Re: guile-config and other packages compiling against guile

[Rob Browning]

Greg Troxel <address@hidden> writes:

>   test -f $(guile-config info pkgincludedir)/gh.h
>
> I see your point, but this feels kludgy and not how other programs
> behave, or at least not how I think they behave.

Sure.  I just meant this as an example.  I think it'd be more
reasonable to have something like "guile-config libs" just (exit 1) if
the libs aren't actually there.

> How does glib (1) handle this?  There is glib-config.   I can't tell,
> because on NetBSD I simply get all of glib, so either it works or it's
> all not present, including glib-config.  So I  really mean how does
> Debian handle glib-config in glib1?

I doubt there's much of an issue since glib-config probably isn't as
likely to be useful when the headers and .so links aren't installed.

With guile I had been thinking that it might be useful, for example,
to be able to find out the guile version, or the location to install
.scm files, even if you don't care about compiling anything.  However,
the more I think about this and look at the output of at least the
current "guile-config info", the more it seems like a mostly
theoretical argument.

For example, if you want to know the version, you can always just ask
guile:

  guile -c '(display (version))'

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4