From: ChenQi <Qi.Chen@windriver.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "MacLeod, Randy" <Randy.Macleod@windriver.com>
Subject: go-mod.bbclass and gomod:// do not have all sources codes available after do_unpack
Date: Mon, 2 Feb 2026 17:35:52 +0800 [thread overview]
Message-ID: <264f0cef-de05-4515-bd33-71c136e01b46@windriver.com> (raw)
Hi All,
When I was checking recent nerdctl issue about rm_work failure, I found
that our gomod handling has some problem.
In short, source codes are not available after do_unpack. They are only
put in place during do_compile.
I think that's why go-mod.bbclass has:
"""
addtask do_compile before do_populate_lic
"""
But this is quite a workaround. do_populate_lic is not the only one that
need to have full source codes.
For example, meta/classes/archiver.bbclass needs sources codes. There
must be other classes that assume sources are there after do_unpack and
modified sources are there after do_patch.
Another big problem is patching. When source codes are only there at
do_compile, this means we cannot patch it. But Yocto should have full
control of the sources, we need to be able to patch any file we want.
In summary, from what I see, the current gomod mechanism does not meet
Yocto's requirement of fully controlling the sources.
I'm bringing this problem up to have more discussion.
Regards,
Qi
next reply other threads:[~2026-02-02 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 9:35 ChenQi [this message]
2026-02-04 8:59 ` [OE-core] go-mod.bbclass and gomod:// do not have all sources codes available after do_unpack Christian Lindeberg
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=264f0cef-de05-4515-bd33-71c136e01b46@windriver.com \
--to=qi.chen@windriver.com \
--cc=Randy.Macleod@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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