From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Re: Git operations during parse
To: bitbake-devel@lists.openembedded.org
From: david.weidenkopf@arthrex.com
X-Originating-Location: Santa Barbara, California, US (184.189.228.123)
X-Originating-Platform: Windows Chrome 93
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Mon, 13 Sep 2021 16:08:06 -0700
References: <0c08eb02be04e948204db6200fbd3312f38ff1ab.camel@linuxfoundation.org>
In-Reply-To: <0c08eb02be04e948204db6200fbd3312f38ff1ab.camel@linuxfoundation.org>
Message-ID: <25324.1631574486288023043@lists.openembedded.org>
Content-Type: multipart/alternative; boundary="o9XEF8p4Kf7xqPkfDaNO"

--o9XEF8p4Kf7xqPkfDaNO
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Thanks! Are there particular variables that play a role in avoiding network=
 operations during parse? Is it SRCREV? BB_NO_NETWORK doesn't seem right fo=
r our use case. We want the build to update from our repos during fetch, ju=
st not during parsing.

--o9XEF8p4Kf7xqPkfDaNO
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Thanks! Are there particular variables that play a role in avoiding network=
 operations during parse? Is it SRCREV? BB_NO_NETWORK doesn't seem right fo=
r our use case. We want the build to update from our repos during fetch, ju=
st not during parsing.<br />

--o9XEF8p4Kf7xqPkfDaNO--