From: Alexandre Oliva (oliva@dcc.unicamp.br)
Date: Sun Jan 31 1999 - 01:01:25 EST
On Jan 26, 1999, Erez Zadok <ezk@cs.columbia.edu> wrote:
> In message <or7lu9ub3d.fsf@araguaia.dcc.unicamp.br>, Alexandre Oliva writes:
>> Should we disable this by default, and create a configure option to
>> enable it? Or should we just disable this completely, based on the
>> assumption that ldconfig is only supposed to speed things up, and
>> such optimizations should be left up to the sysadmin?
> I prefer a configure option that would add the execution of ldconfig to make
> install. I also don't like that ldconfig is run regardless of my running as
> non-root. If we don't want to break functionality for those who are used to
> this behavior, the I'd go for enabling ldconfig run by default, unless a
> --disable-FOO option was invoked.
After some reading of documentation, it seems to me that ldconfig, as
run by libtool, will only try to update caches, not actually add any
directories as `trusted' to any directory list. Therefore, it seems
to me that it is safe to run it, and I no longer see any reason to
modify this behavior, except maybe by only running it as root, or
telling a non-root user that he doesn't have to worry if that command
fails.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:53 EDT