Mailinglist Archive: opensuse-factory (422 mails)

[Rob OpenSuSE <rob.opensuse.linux@xxxxxxxxxxxxxx>]

2009/1/21 Dave Plater <dave.plater@xxxxxxxxxxx>:
> If I do that in bash.bashrc.local then maybe it might work?

I don't think so, I was suggesting an alteration to nullify the proxy
strings, specifically aimed to clean up the package management
behaviour, when the proxy usage is turned off.  That is to rely soley
on what's written in ~root/.curlrc, avoiding user http_proxy settings.

The behaviour of the environment, is performance and ease for
programmer oriented.  Effectively it is an  in-process memory cache of
configuration oriented settings, without reading disk files, or
accessing a database.  Knowledgeable experienced users do not expect,
changes to those settings to be immediately effective.


info:/bash/Bash Startup Files
Suggests possibily of defining BASH_ENV, a startup file that would be
read by non-interactive /bin/bash scripts.
However there's no guarantee this would be run.

The specification of char ** environ as a variable, makes it hard to
provide new backends with more sophisticated configurable cache-ing
behaviour via getenv/putenv/setenv/unsetenv/clearenv functions.   So
software suites which need sophisticated configuration, use other
methods.  For example browsers provide ways for Network Admin to
configure automatic proxy detection.

Hopefully these explanations will help you understand the explanation
Katarina Machalkova gave earlier in the thread.  If not then some
generalised reading on concepts of processes, environment will make
things clearer.
-- 
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx