On Tue, Mar 1, 2022 at 02:14 PM, Bruce Ashfield wrote:<br />
<blockquote>On Tue, Mar 1, 2022 at 6:42 AM Andrei Gherzan &lt;andrei@gherzan.com&gt; wrote:<br />
<blockquote><br />On Tue, 1 Mar 2022, at 01:55, Bruce Ashfield wrote:<br />
<blockquote>On Mon, Feb 28, 2022 at 8:17 PM Bruce Ashfield via<br />lists.openembedded.org<br />&lt;bruce.ashfield=gmail.com@lists.openembedded.org&gt; wrote:<br />
<blockquote><br />On Mon, Feb 28, 2022 at 6:54 PM Andrei Gherzan &lt;andrei@gherzan.com&gt; wrote:<br />
<blockquote><br />From: Andrei Gherzan &lt;andrei.gherzan@huawei.com&gt;<br /><br />Compile pulls in the go.mod list requiring network. Without this, do<br />compile would fail with a similar error to the following:<br /><br />dial tcp: lookup proxy.golang.org: Temporary failure in name resolution</blockquote>
This is something that needs to be carried in your own layers, IMHO it<br />isn't appropriate for core.<br /><br />It isn't about the fetching, it is the entire gap in functionality<br />that we are missing if go starts fetching dependencies during compile.</blockquote>
A further thought is that if this is for go.mod issues, there is the<br />go-mod.bbclass.<br /><br />Perhaps enabling it in that class and doing a bbwarn about go fetching<br />dependencies would be appropriate ?<br /><br />Otherwise, someone may not know that this is happening and that a no<br />network configuration has no chance of working.</blockquote>
I reckon that is reasonable. I'll personally go down the recipe level to workaround this change but understanding and agreeing with the reasoning behind this change, I want to invest a bit into trying to find a proper solution in the core. Bruce, I know you invested a fair amount of time into this already. Would you be willing to sync up and see how we can work together in tackling this?</blockquote>
Definitely, more ideas are good. In fact, I think there are probably<br />several approaches that can co-exist, depending on what a<br />recipe/developer needs.<br /><br />I'm in the Eastern time zone here, and will try and grab folks on IRC<br />to have a level set<br /><br />Bruce<br /><br />
<blockquote>Added Zyga to CC as he is also interested in this as part of his go development activities.<br /><br />Thanks,<br />Andrei</blockquote>
<br /><br />-- <br />- Thou shalt not follow the NULL pointer, for chaos and madness await<br />thee at its end<br />- "Use the force Harry" - Gandalf, Star Trek II</blockquote>
<div>The problem in allowing downloads during compile (e.g. by go) is, that it leads to non-reproducable builds. I'm currently facing the same issue and would like to have a reproducable go *offline* build.</div>
<div>I would like to propose two ideas to workaround the go-compile fetching issue:</div>
<div>&nbsp;</div>
<div>First:</div>
<div>- Fetch go-dependencies using go.mod file from 'proxy.golang.org' (e.g. by writing a seperate go fetcher or a wget-fetcher) and unpack the dependencies into go projects 'vendor' folder. This forces go to compile offline. However, one have to generate the 'modules.txt' file in the vendor folder 'manually' during unpack. This is error prone, as there is no official documentation how this format should look like. Anyway, I've tried this approach and it works for me.</div>
<div>&nbsp;</div>
<div>Second:</div>
<div>- Fetch go-dependencies using go.mod file from 'proxy.golang.org' (e.g. by writing a seperate go fetcher) and unpack the dependencies into a local (workdir) go-path. This seemed a good solution for me as the go-path is well defined. But for some reason 'go'&nbsp; fetches the zip-files during compile into it's download-cache AGAIN, even if the source is already unpacked in the go-path. I'll assume this is required to verify the source files integrity?! With this approach one have to adapt 'go' to suppress this download behaviour.</div>
<div>&nbsp;</div>
<div>Please let me know your opinion on these two approaches.</div>