Peter Poeml wrote:
YaST could simply read the current setting from /etc/sysconfig/proxy when it starts, and put them into the environment, so they would be used by both libcurl and aria2c.
This would break with the principle of least surprise for some users, who expect the current *environment* to be decisive; things to do in a shell like # http_proxy= yast2 or # http_proxy=http://different-proxy.example.com:3128/ yast2 to temporarily override a setting would no longer be working.
I tend to agree, however, that most "normal" users would benefit from yast2 reading the settings from /etc/sysconfig/proxy afresh, thus ignoring the enviromnent. It would give *those* users what they expect, I guess.
Right now, the MediaAria backend is just an extended MediaCurl. So when attaching a http media, it reads Sysconfig, and sets the proxy from there, unless the user override it in the url. However, I am not sure how libcurl or aria handle the environment variable or curlrc. Duncan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org