Building behind a firewall/proxy

All,

For the Yocto 1.1 release we want to ease the pain of getting set up to build behind a firewall.

I have a series of patches under development to run a one hit sanity test which tries to verify the user can fetch and in the case of failure point the user to a wiki page where we'd document common causes of fetch failures.

We're also going to look at the site.conf file, which can be used to specify proxy settings and other site specific settings such MIRRORS, and ensure that it can easily be edited to help people get set up.

It'd be great if people who operate behind a proxy/firewall can help us document the steps they had to take to work around this.

Further if you have other ideas as to how we can help make this process less painful please let us know.

Op 28 jun 2011, om 22:14 heeft Joshua Lock het volgende geschreven:

Quoted 17 lines

All,

For the Yocto 1.1 release we want to ease the pain of getting set up to build behind a firewall.

I have a series of patches under development to run a one hit sanity test which tries to verify the user can fetch and in the case of failure point the user to a wiki page where we'd document common causes of fetch failures.

We're also going to look at the site.conf file, which can be used to specify proxy settings and other site specific settings such MIRRORS, and ensure that it can easily be edited to help people get set up.

It'd be great if people who operate behind a proxy/firewall can help us document the steps they had to take to work around this.

Quoted 2 lines

Further if you have other ideas as to how we can help make this process less painful please let us know.

This is what I'm using inside TI: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/setup-scripts/tree/oebb.sh?h=oe-core

It grew organically, so grepping for 'proxy' is your best bet :)

All,

For the Yocto 1.1 release we want to ease the pain of getting set up to build behind a firewall.

I have a series of patches under development to run a one hit sanity test which tries to verify the user can fetch and in the case of failure point the user to a wiki page where we'd document common causes of fetch failures.

We're also going to look at the site.conf file, which can be used to specify proxy settings and other site specific settings such MIRRORS, and ensure that it can easily be edited to help people get set up.

It'd be great if people who operate behind a proxy/firewall can help us document the steps they had to take to work around this.

Further if you have other ideas as to how we can help make this process less painful please let us know.

Quoted 14 lines · Joshua Lock

All,

For the Yocto 1.1 release we want to ease the pain of getting set up to build behind a firewall.

I have a series of patches under development to run a one hit sanity test which tries to verify the user can fetch and in the case of failure point the user to a wiki page where we'd document common causes of fetch failures.

We're also going to look at the site.conf file, which can be used to specify proxy settings and other site specific settings such MIRRORS, and ensure that it can easily be edited to help people get set up.

Quoted 5 lines

It'd be great if people who operate behind a proxy/firewall can help us document the steps they had to take to work around this.

Further if you have other ideas as to how we can help make this process less painful please let us know.

Is SOCKS5_PASSWD SOCKS5_USER in the default BB_ENV_EXTRAWHITE list atm?
If not, it needs to be.