http://bugzilla.novell.com/show_bug.cgi?id=558539 http://bugzilla.novell.com/show_bug.cgi?id=558539#c2 --- Comment #2 from Richard Bos <richard.bos@xs4all.nl> 2009-11-28 16:28:02 UTC ---
We need to figure out why /etc/sysconfig/proxy overrules the environment. I guess this was done to immediately reflect changes done by the YaST proxy configuration. So we'd need a fix for that usecase.
Hmm, that is a good point. You don't want a user to exit YaST and its related shell, to have him or her re-enter the shell and YaST to have the proxy variable reread. Zypper should not read /etc/sysconfig/proxy, that is more a task for YaST. As YaST controls and knows when /etc/sysconfig/proxy is changed, and also knows when the related proxy variables are changed, YaST should instruct zypper how to deal with the proxy. This seems possible with aria2c --http-proxy=HOST:PORT argument. In normal cases YaST and hence Zypper should always use the environment variables, in the (rare ;) ) situation that the user changes the proxy settings, YaST should overwrite the environment settings and instruct aria2c via the --http-proxy=HOST:PORT how to deal with the proxy. Or perhaps YaST can change the value of the environment variable http_proxy while running? Hopefully this is can be implemented in YaST?! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.