All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Scott Garman <scott.a.garman@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: Introduction and Request for HTTP Git Access
Date: Tue, 09 Nov 2010 13:31:40 -0500	[thread overview]
Message-ID: <20101109183140.GC8761@denix.org> (raw)
In-Reply-To: <4CD98D69.5020003@intel.com>

On Tue, Nov 09, 2010 at 10:05:29AM -0800, Scott Garman wrote:
> On 11/09/2010 08:31 AM, Ryan_D_Phillips@Dell.com wrote:
>> Good Day!
>>
>> My name is Ryan Phillips (irc: rphillips), a former Gentoo Linux
>> Developer, currently a software developer architecting an embedded
>> firmware solution on OE for my employer. With the release of Yocto,
>> we are extremely interested in trying it out and possibly
>> contributing to the project. My cohort working with me is Sean Hudson
>> (irc: darknighte), and is someone who you may see contributions from
>> as well.
>>
>> A major stumbling block we must work around is the restrictive
>> firewall and git checkouts. We have found out the git-http-backend
>> works extremely well, and are requesting this support on
>> git.pokylinux.org. We suspect other people within larger corporations
>> would have a similar problem, and by adding this support would help
>> the community at large.
>>
>> I can help out in any way possible.
>
> Hi Ryan,
>
> I just added a page to our wiki that details instructions for getting up
> and running with Poky behind a SOCKS proxy server:
>
> https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy

Hmm, quite interesting. Looks like Richard finally saw the light at the end of 
the tunnel, so to speak, :) and you guys started using standard environment 
variables - http_proxy, ftp_proxy, no_proxy and GIT_PROXY_COMMAND, passing 
them through bitbake to the external fetchers. At least it appears this way 
from reading the above Wiki instructions... As we have almost the same exact 
instructions to work inside TI.

2 years ago I tried convincing Richard to switch from non-standard HTTP_PROXY* 
and FTP_PROXY* bitbake variables to the standard ones, but wasn't successful[1].
So I had to fork bitbake and make the changes myself for our Arago Project, 
rebasing them later against the final 1.8.18 version of bitbake[2].

Richard, that's what I mentioned during OEDEM couple weeks ago. I was going to 
squash my changes, rebase them against 1.10 or master and post them to the 
bitbake mailing list...

[1] http://thread.gmane.org/gmane.comp.handhelds.openembedded/19716
[2] http://arago-project.org/git/?p=arago-bitbake.git;a=summary

-- 
Denys


  reply	other threads:[~2010-11-09 18:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 16:31 Introduction and Request for HTTP Git Access Ryan_D_Phillips
2010-11-09 17:02 ` Denys Dmytriyenko
2010-11-09 17:22   ` Darren Hart
2010-11-09 17:34     ` Ryan D Phillips
2010-11-09 18:06       ` Denys Dmytriyenko
2010-11-09 18:35         ` Darren Hart
2010-11-09 18:05 ` Scott Garman
2010-11-09 18:31   ` Denys Dmytriyenko [this message]
2010-11-09 21:46     ` Ryan D Phillips
2010-11-10  0:10       ` Richard Purdie

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=20101109183140.GC8761@denix.org \
    --to=denis@denix.org \
    --cc=poky@yoctoproject.org \
    --cc=scott.a.garman@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.