From: Darren Hart <dvhart@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Poky <poky@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 8/9] meta-yocto: Document new oe-git-proxy in site.conf.sample
Date: Tue, 05 Feb 2013 16:29:57 -0800 [thread overview]
Message-ID: <5111A405.2020308@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKqt0ZwcyOzCZYVqPt_tuSqk-=PJAX22sP2V2=P-0a94Uw@mail.gmail.com>
On 02/05/2013 04:24 PM, Otavio Salvador wrote:
> On Tue, Feb 5, 2013 at 8:52 PM, Darren Hart <dvhart@linux.intel.com> wrote:
>> The new oe-git-proxy.sh should address all git proxying needs. Document
>> its usage in meta-yocto/conf/site.conf.sample and remove references to
>> the old mechanisms.
>>
>> V2: Separate out the meta-yocto changes from the oe-core changes
>>
>> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
>> ---
>> meta-yocto/conf/site.conf.sample | 35 +++++++++--------------------------
>> 1 files changed, 9 insertions(+), 26 deletions(-)
>>
>> diff --git a/meta-yocto/conf/site.conf.sample b/meta-yocto/conf/site.conf.sample
>> index 68d1da9..2834702 100644
>> --- a/meta-yocto/conf/site.conf.sample
>> +++ b/meta-yocto/conf/site.conf.sample
>> @@ -16,32 +16,15 @@ SCONF_VERSION = "1"
>> #http-proxy-port = 81
>> #
>>
>> -# Uncomment to cause git to use the proxy host specificed
>> -# although this only works for http
>> -#GIT_PROXY_HOST = "proxy.example.com"
>> -#GIT_PROXY_PORT = "81"
>> -#export GIT_PROXY_COMMAND = "${COREBASE}/scripts/oe-git-proxy-command"
>> -
>> -# Set to yes to have a gitconfig generated for handling proxies; you
>> -# might not want this if you have all that set in your global git
>> -# configuration. If you don't enable it, the rest of the entries
>> -# (_PROXY_IGNORE, etc) don't really work that well
>> -#GIT_CORE_CONFIG = "Yes"
>> -
>> -# Space separate list of hosts to ignore for GIT proxy
>> -#GIT_PROXY_IGNORE = "host.server.com another.server.com"
>> -
>> -# If SOCKS is available run the following command to comple a simple transport
>> -# gcc scripts/oe-git-proxy-socks.c -o oe-git-proxy-socks
>> -# and then share that binary somewhere in PATH, then use the following settings
>> -#GIT_PROXY_HOST = "proxy.example.com"
>> -#GIT_PROXY_PORT = "81"
>> -
>> -# GIT_PROXY_COMMAND is used by git to override all proxy settings from
>> -# configuration files, so we prefix OE_ to avoid breaking havoc on the
>> -# generated (or local) gitconfig's.
>> -#OE_GIT_PROXY_COMMAND = "${COREBASE}/scripts/oe-git-proxy-socks-command"
>> -
>> +# To use git with a proxy, you must use an external git proxy command, such as
>> +# the one provided by scripts/oe-git-proxy.sh. To use this script, copy it to
>> +# your PATH and uncomment the following:
>> +#GIT_PROXY_COMMAND="oe-git-proxy.sh"
>
> .sh
Fixed
> A similar change ought to be done for oe-core .sample, no?
I didn't see any git proxy documentation there and no conf.sample files
in oe-core at all. Perhaps someone would like to add a site.conf.sample
for oe-core?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-02-06 0:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 22:52 [PATCH V2 0/9] Git fetcher and proxy handling updates Darren Hart
2013-02-05 22:52 ` [PATCH 1/9] bitbake: fetch2: Print the complete SRCREV variable name when INVALID Darren Hart
2013-02-05 22:52 ` [PATCH 2/9] bitbake: fetch2: Export upper and lower case environment variables Darren Hart
2013-02-05 22:52 ` [PATCH 3/9] bitbake: fetch2: Remove broken git variables from the environment Darren Hart
2013-02-05 22:52 ` [PATCH 4/9] oe-buildenv-internal: Remove GIT variables from BB_ENV_EXTRAWHITE Darren Hart
2013-02-05 22:52 ` [PATCH 5/9] oe-buildenv-internal: Add upper and lower case proxy vars to BB_ENV_EXTRAWHITE Darren Hart
2013-02-05 22:52 ` [PATCH 6/9] base.bbclass: Remove generate_git_config() Darren Hart
2013-02-05 22:52 ` [PATCH 7/9] oe-git-proxy: Add a new comprehensive git proxy script Darren Hart
2013-02-05 23:51 ` Otavio Salvador
2013-02-06 0:04 ` Darren Hart
2013-02-06 0:09 ` Otavio Salvador
2013-02-06 0:16 ` Darren Hart
2013-02-05 22:52 ` [PATCH 8/9] meta-yocto: Document new oe-git-proxy in site.conf.sample Darren Hart
2013-02-06 0:24 ` Otavio Salvador
2013-02-06 0:29 ` Darren Hart [this message]
2013-02-05 22:52 ` [PATCH 9/9] oe-git-proxy*: Remove previous git proxy solutions Darren Hart
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=5111A405.2020308@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=poky@yoctoproject.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