Instructions say to set http_proxy et al in environment but this is a Bad Idea

[Ian Wells]

If you set http_proxy in the environment:

- apt-get respects it, which often means any misconfiguration is hidden (it needs Acquire::http::proxy to be set if you need a proxy, but ignores this setting in favour of the environment if there are settings there)
- puppet apply site.pp *does not work* if http_proxy is set.

The instructions should tell people able $proxy and Acquire::http::proxy, very carefully ensure that commandlines that must be run either take arguments or are documented in the form "env=value command args", and should explicitly warn about setting http_proxy with export, in /etc/environment or in ~/.profile or ~/.bashrc .

I would change this, but then in fact I did change this, and someone changed it back for the Grizzly release, so it's someone else's turn now.