Mailinglist Archive: zypp-devel (58 mails)

[Katarina Machalkova <kmachalkova@xxxxxxx>]

Hi, zypp hackers :)

When it comes to $http_proxy * & friends handling, libzypp uses a mix of two 
or even three approaches: 

* it honors $http_proxy from the environment, probably because libcurl does so 
and libzypp explicitely does not unset this variable
* in addition to that, it reads /root/.curlrc and gets proxy URL (optionally 
also user/passwd) from there
* last, but not least, proxy can be provided as a part of repository URL

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@xxxxxxxxxxxxxx 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 
complaints on Factory, it would be much more comfortable for those using GUI 
package managers, as they wouldn't have to re-login in order to apply their 
proxy setting

Proxy as a part of repository URL is a cherry on top of the cake, but I doubt 
many users know about this option and make real use of it. 

B.

*) and other *TP proxies, I'm referencing http only because of simplicity
-- 
   \\\\\              Katarina Machalkova    
  \\\\\\\__o          YaST developer
__\\\\\\\'/_          & hedgehog painter
-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx