Re: RFC: Add http_proxy and ftp_proxy to BitBake white list

[Denys Dmytriyenko <denis@denix.org>]

On Wed, Nov 12, 2008 at 01:44:16PM -0500, Denys Dmytriyenko wrote:
> On Sun, Nov 09, 2008 at 01:22:14PM +0000, Richard Purdie wrote:
> > 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.
> 
> Why not use the standard $no_proxy environment variable to list addresses 
> inside the firewall?
> 
> > 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.
> 
> Looks redundant, as it can be achieved like this:
> 
> $ export http_proxy=proxy.company.com:80
> $ export no_proxy=company.com,interweb.net
> 
> > > 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.
> 
> Even though I'd prefer it to be fixed properly with 15-year-old http_proxy and 
> no_proxy environment variables, it does not matter too much, as long as any 
> kind of http/ftp proxy support is merged into upstream BitBake, please. :) 
> Thanks.

And speaking of proxies - since recently you removed GIT_PROXY_COMMAND from 
the list of exported variables, what's the correct method of using Git behind 
the proxy with BitBake?

-- 
Denys