All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Carretero" <cJ-yocto@zougloub.eu>
To: "Mingrui Ren" <jiladahe1997@gmail.com>,
	richard.purdie@linuxfoundation.org
Cc: yocto@lists.yoctoproject.org,
	bitbake-devel@lists.openembedded.org,
	poky@lists.yoctoproject.org, ross.burton@arm.com
Subject: Re: [yocto] [PATCH v2] bitbake/fetch2: Add a new variable 'BB_FETCH_ENV' to export Fetcher env
Date: Mon, 14 Mar 2022 23:34:19 -0400	[thread overview]
Message-ID: <20220314233413.76f85dc0@pouet.cJ> (raw)
In-Reply-To: <7ba30db0-c7db-b1c0-5243-86d5df789f17@gmail.com>

Hi Mingrui, Richard,


On Sat, 11 Sep 2021 11:42:44 +0800
"Mingrui Ren" <jiladahe1997@gmail.com> wrote:

> On 06/09/2021 17:41, Richard Purdie wrote:
> [...]
> > Why is this a problem? You need to state what the problem is
> [...]
> I think it's a good a feature if we could add custom variables into 
> fetcher. For example,
> we could fetch private code by adding username or password, or we could 
> adding custom
> proxy tools.

I have found myself using a sed one-liner to alter that variable list
in the fetcher code in order to pass through to git the
GIT_CONFIG_GLOBAL environment variable, the goal being to do git URL
rewrites via the git configuration (to pass HTTP credentials, or to use
a local repo because I didn't want to bother keeping obscure VPNs
online); it was the shortest way I could think of to achieve this.
Alternatively I could have used a PATH modification with a host tool
wrapper.
Ideally I would prefer adding a KEY += value line to a site.conf.


Best regards,

-- 
Jérôme


      reply	other threads:[~2022-03-15  3:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23  7:18 [PATCH v2] bitbake/fetch2: Add a new variable 'BB_FETCH_ENV' to export Fetcher env Mingrui Ren
2021-09-06  9:41 ` Richard Purdie
2021-09-11  3:42   ` Mingrui Ren
2022-03-15  3:34     ` Jérôme Carretero [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=20220314233413.76f85dc0@pouet.cJ \
    --to=cj-yocto@zougloub.eu \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=jiladahe1997@gmail.com \
    --cc=poky@lists.yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@arm.com \
    --cc=yocto@lists.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 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.