Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Building behind a firewall/proxy
Date: Wed, 29 Jun 2011 15:19:56 -0700	[thread overview]
Message-ID: <1309386002.24735.6.camel@scimitar> (raw)
In-Reply-To: <4E0A4BA0.9050409@mentor.com>

On Tue, 2011-06-28 at 14:46 -0700, Tom Rini wrote:
> On 06/28/2011 01:14 PM, Joshua Lock wrote:
> > 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.
> 
> Is SOCKS5_PASSWD SOCKS5_USER in the default BB_ENV_EXTRAWHITE list atm?
>  If not, it needs to be.
> 

Noted, thanks Tom.

Joshua
-- 
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre




      reply	other threads:[~2011-06-29 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 20:14 Building behind a firewall/proxy Joshua Lock
2011-06-28 20:20 ` Koen Kooi
2011-06-29 22:18   ` Joshua Lock
2011-06-28 21:46 ` Tom Rini
2011-06-29 22:19   ` Joshua Lock [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1309386002.24735.6.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox