With the three environment variables "HTTP_PROXY, FTP_PROXY, and RSYNC_PROXY" set in /etc/profile, or by exporting to the environment, 'emerge --sync' will succeed where 'emerge <packagename>' will fail. Adding these three environment variables to make.conf does not change this failure, but a lowercase 'http_proxy' and 'ftp_proxy' to the make.conf will allow 'emerge <packagename>' to work. This bug filing assumes that emerge has the desire to: 1. Work with the standard environment variables HTTP_PROXY and FTP_PROXY as they have become a standard for many console based applications that connect through the internet. 2. Continue with the standard that environment variables as well as variables set in make.conf are capatalized. Reproducible: Always Steps to Reproduce: 1.Assign a working HTTP_PROXY od FTP_PROXY in /etc/profile, make.conf, or by use of 'export HTTP_PROXY="proxyname:port" 2. try to emerge a package through the assigned proxy. Actual Results: emerge will have a connection error. Expected Results: emerge should succeed. Note that if a "PROXY" environment variable is set, emerge (with wget) will fail, but running "wget <package filename>" will succeed.
You can probably work around this if you put the PROXY variable into a new file in /etc/env.d and then run env-update. That will put the variable into /etc/profile.env so that portage actually uses it.
Portage doesn't use those variables at all. They are wget environment variables.
