From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: fabien.proriolpatch@kazoe.org, bitbake-devel@lists.openembedded.org
Cc: Fabien Proriol <fabien.proriol@jdsu.com>
Subject: Re: [PATCH] bb.fetch.git: add a way to avoid git protocol, and force http or https mirrors
Date: Tue, 31 May 2016 14:50:13 +0100 [thread overview]
Message-ID: <1464702613.3814.2.camel@linuxfoundation.org> (raw)
In-Reply-To: <1464700684-24169-1-git-send-email-fabien.proriolpatch@kazoe.org>
On Tue, 2016-05-31 at 15:18 +0200, fabien.proriolpatch@kazoe.org wrote:
> From: Fabien Proriol <fabien.proriol@jdsu.com>
>
> This patch add the possibility to bitbake to avoid git protocol to
> fetch sources.
> This is usefull in some network with firewall blocking git port.
>
> When BB_GIT_PROTOCOL_FIREWALL is set, the PROTOCOL_MIRRORS table is
> used to find the new protocol (http or https) and the new host (if
> different) to used.
>
> BB_GIT_PROTOCOL_FIREWALL can also contains a list of host accepted.
> This is usefull for exemple, if we use local git repository inside
> the network.
>
> Exemple usage:
> # Avoid all git protocol
> BB_GIT_PROTOCOL_FIREWALL = "1"
>
> # Avoid git protocol, except for srv1 and srv2 in local network
> BB_GIT_PROTOCOL_FIREWALL = "srv1.mydomain.com;srv2.mydomain.com"
Why not use the more generic MIRRORS and PREMIRRORS for this? If they
can't support this, we likely should figure out a way to make them work
for it rather than adding new fetcher specific variables.
Cheers,
Richard
next prev parent reply other threads:[~2016-05-31 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 13:18 [PATCH] bb.fetch.git: add a way to avoid git protocol, and force http or https mirrors fabien.proriolpatch
2016-05-31 13:39 ` Olof Johansson
2016-05-31 13:50 ` Richard Purdie [this message]
2017-07-24 21:04 ` Andre McCurdy
2017-07-25 14:43 ` Mark Hatle
2017-07-25 19:30 ` Andre McCurdy
2017-07-25 22:19 ` Richard Purdie
2017-07-26 12:58 ` Mark Hatle
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=1464702613.3814.2.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=fabien.proriol@jdsu.com \
--cc=fabien.proriolpatch@kazoe.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 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.