From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: lukas.funke-oss@weidmueller.com,
openembedded-core@lists.openembedded.org
Cc: Bruce Ashfield <bruce.ashfield@gmail.com>,
Martin Jansa <martin.jansa@gmail.com>,
Lukas Funke <lukas.funke@weidmueller.com>
Subject: Re: [OE-Core][PATCH v2 0/4] recipetool: Add handler to create go recipes
Date: Sun, 22 Oct 2023 20:34:47 +0200 [thread overview]
Message-ID: <a9389814-affd-4bce-85b9-e3a4555a684e@gmail.com> (raw)
In-Reply-To: <20231017132647.352938-1-lukas.funke-oss@weidmueller.com>
Hey Lukas,
Thanks a lot for the patch. A few questions/comments from my initial
test below.
- I tried it with a go-based backend I have by providing ssh URL to
github. It seems like the GO_IMPORT is set to a module name from go.mod
of my project, which of course fails to fetch it like that, because it's
not a valid URL. How is it supposed to be used?
- I've got about 20 lines like:
INFO: Please add the following line for
'vendor/google.golang.org/protobuf/LICENSE' to a
'lib/recipetool/licenses.csv' and replace `Unknown` with the license:
02d4002e9171d41a8fad93aa7faf3956,Unknown
INFO: Please add the following line for
'vendor/gopkg.in/yaml.v3/LICENSE' to a 'lib/recipetool/licenses.csv' and
replace `Unknown` with the license:
3c91c17266710e16afdbb2b6d15c761c,Unknown
I believe I have to go through all of them manually and set a proper
license in the recipe. Still the questions arises, what should be a
better way to reduce amount of this work? Adding more hashes/licenses to
lib/recipetool/licenses.csv would be a way to go? I'm just afraid that
file might explode if we use it like that...
- Could please clarify where does the version from go.mod hide? Is it
taken directly from go.mod? I'm trying to understand what should be the
workflow when a module version should be bumped up in the go.mod. Will
that be reflected in the recipe in any way?
Thanks,
Slava
On 17.10.2023 15:26, lukas.funke-oss@weidmueller.com wrote:
> From: Lukas Funke <lukas.funke@weidmueller.com>
>
> This patch series adds a recipetool handler in order to create 'go' recipes.
> Each recipe contains a list of dependencies in their SRC_URI
> variable which are derived from the projects `go.mod` file. For each
> dependency the corresponding license file uri/hash is added.
>
> The recipe may not work ad-hoc, but is a good starting point to create
> a working recipe and have a working offline-build.
>
> Lukas Funke (4):
> classes: go-vendor: Add go-vendor class
> selftest: recipetool: Add test for go recipe handler
> recipetool: Ignore *.go files while scanning for licenses
> recipetool: Add handler to create go recipes
>
> meta/classes/go-vendor.bbclass | 135 ++++
> meta/lib/oeqa/selftest/cases/recipetool.py | 163 +++++
> scripts/lib/recipetool/create.py | 2 +-
> scripts/lib/recipetool/create_go.py | 730 +++++++++++++++++++++
> 4 files changed, 1029 insertions(+), 1 deletion(-)
> create mode 100644 meta/classes/go-vendor.bbclass
> create mode 100644 scripts/lib/recipetool/create_go.py
>
next prev parent reply other threads:[~2023-10-22 18:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 13:26 [OE-Core][PATCH v2 0/4] recipetool: Add handler to create go recipes lukas.funke-oss
2023-10-17 13:26 ` [OE-Core][PATCH v2 1/4] classes: go-vendor: Add go-vendor class lukas.funke-oss
2023-10-18 6:36 ` Ulrich Ölmann
2023-10-17 13:26 ` [OE-Core][PATCH v2 2/4] selftest: recipetool: Add test for go recipe handler lukas.funke-oss
2023-10-17 13:26 ` [OE-Core][PATCH v2 3/4] recipetool: Ignore *.go files while scanning for licenses lukas.funke-oss
2023-10-17 13:26 ` [OE-Core][PATCH v2 4/4] recipetool: Add handler to create go recipes lukas.funke-oss
2023-10-17 13:53 ` Richard Purdie
2023-10-17 14:00 ` Lukas Funke
2023-10-17 22:23 ` Richard Purdie
2023-10-22 18:34 ` Vyacheslav Yurkov [this message]
2023-10-23 12:18 ` [OE-Core][PATCH v2 0/4] " Lukas Funke
2023-10-23 17:05 ` Vyacheslav Yurkov
2023-10-24 6:19 ` Lukas Funke
2023-10-24 7:32 ` Vyacheslav Yurkov
2023-10-23 18:06 ` Vyacheslav Yurkov
2023-10-24 6:33 ` Lukas Funke
2023-10-24 7:12 ` Vyacheslav Yurkov
2023-10-24 8:27 ` Lukas Funke
2023-10-27 21:32 ` Peter Kjellerstedt
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=a9389814-affd-4bce-85b9-e3a4555a684e@gmail.com \
--to=uvv.mail@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=lukas.funke-oss@weidmueller.com \
--cc=lukas.funke@weidmueller.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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