On 27-Feb-00 Chuck Robey wrote:
> Some stuff, like tclsh, could have a default link, say from tclsh to
> tclsh8.2, or allow a user to set that. That could be a local option, but
> it's icing on the cake as far as I'm concerned. The only real thing I
> would be after is the ability to stick the config file locations in the
> places that the original developers (and the configuration scripts they
> build with) expect them to be. Anything done as far as executeable names,
> I don't really care too much about.
There are only a few libraries that have a config file to aid
compiling/linking. Of the ones we 'version' (GTK and GLIB) you can set the
GLIB/GTK_CONFIG env. var to tell apps where to find it.
I don't think its possible for tcl since it looks in a given path for a
config file instead of looking for a config file in the path.
---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
