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:18:08 -0700 [thread overview]
Message-ID: <1309385893.24735.5.camel@scimitar> (raw)
In-Reply-To: <B63D1FE8-267F-4551-BF49-0149E6A929AE@dominion.thruhere.net>
On Tue, 2011-06-28 at 22:20 +0200, Koen Kooi wrote:
> Op 28 jun 2011, om 22:14 heeft Joshua Lock het volgende geschreven:
>
> > 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.
>
> 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 :)
Thanks Koen, a useful reference.
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-29 22:21 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 [this message]
2011-06-28 21:46 ` Tom Rini
2011-06-29 22:19 ` Joshua Lock
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=1309385893.24735.5.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