[oe] RFC: Add http_proxy and ftp_proxy to BitBake white list

[Richard Purdie]

Hi Cliff,

On Fri, 2008-11-07 at 14:57 -0500, Cliff Brake wrote:
> I've attempted to merge your patches and test, but the http_proxy is
> still not preserved for wget.  A few notes:
> 
> wget does not pass through runfetchcmd() so exportvars stuff never
> gets called there.
> 
> try_mirror also has some http_proxy stuff, but it does not appear to
> be used by wget.
> 
> wget.py looks at HTTP_PROXY, but why HTTP_PROXY vs http_proxy?  If I
> set HTTP_PROXY in local.conf, it then works.

For various reasons I've now had some experience of using bitbake behind
some pretty strict proxy setups. The problem is that its not as simple
as just setting http_proxy since some addresses need to go through the
proxy but things like a local source mirror might be on an internal
network and therefore shouldn't go through the proxy.

I hence reworked things so you set HTTP_PROXY but can also set
HTTP_PROXY_IGNORE which is a list of base urls which should not use the
proxy. The fetcher code will only set http_proxy to HTTP_PROXY if the
url is not in the ignore list.

FTP_PROXY and ftp_proxy works in a similar way.

> So, is the idea the user has to set HTTP_PROXY in a conf file for wget
> proxy to work?  What are the downsides to using http_proxy from the
> environment?  At any rate, it seems like we have some inconsistencies
> in the various fetcher methods.

The idea is the user sets HTTP_PROXY and optionally HTTP_PROXY_IGNORE to
make http proxying work. I'm planning to make bitbake ignore http_proxy
from the environment due to the problems is causes with mirror servers
behind the proxy.

Hopefully this clears up the intent of the patches, the improvements are
based on real world usage problems.

Cheers,

Richard