On 1/22/2009 at 12:21 PM, Katarina Machalkova
wrote: Hi, zypp hackers :) I'm wondering what is the incentive behind combining all these three approaches, instead of e.g. reading only $http_proxy (curl can already accept URL in the form of http://user:pass@some.proxy.url so we don't necessarily need .curlrc for reading this data - is .curlrc used because we can't effectively setenv. during installation?). Or alternatively, libzypp could read only .curlrc, as it contains all the necessary information and ignore $http_proxy completely. Reading recent user
Maybe worth having a look at libproxy [0]? (libneon uses it already for example) The library's only purpose is getting info from the system and provide the needed information to applications. It get's the configuration from gnome settings, network manager, kde and offers on top of that support of pac files to every application depending on libproxy (jscript parser). The lack of pac support is something I'm missing in many applications. PAC is just more powerful than what you could ever achieve in a envvar. Dominique [0] http://code.google.com/p/libproxy/ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org