From: "Robert Berger" <robert.berger.yocto.user@gmail.com>
To: Irving ST <irving@ssfivy.com>,
Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [yocto] License reporting for golang (and rust)
Date: Tue, 30 Jun 2020 00:32:05 +0300 [thread overview]
Message-ID: <4bafc350-fa80-c4e9-a13f-579484cc389e@gmail.com> (raw)
In-Reply-To: <CAN--ZaUr1C_rKY05_yWuD=A-S7deSvd5gFSYc2ZE-V7vDTkZxw@mail.gmail.com>
Hi,
My comments are in-line
On 22/06/2020 11:53, Irving ST wrote:
> Hello,
>
> I am building a device that uses some Go (and Rust) dependencies. This
> is on Yocto 2.7 / Warrior.
>
> I noticed that after building an image, the generated license.manifest
> and package.manifest (in tmp/deploy/licenses/) does not contain any
> mention of go packages or rust crates. The go packages seem to
> generate directories in tmp/deploy/licenses/ but they do not seem to
> be reported in the final image.
On dunfell 3.1.1 I see this:
licenses/
└── github.com-influxdata-influxdb
├── generic_MIT
├── LICENSE
└── recipeinfo
which is wrong, since I would need to add all the licenses of all the
dependencies golang pulls in as well to the recipe. It's shows only the
top level license.
In my license manifest I do have the influxdb:
tmp/deploy/licenses/image-influxdb-from-source-container-x86-64-20200629205620/license.manifest
PACKAGE NAME: github.com-influxdata-influxdb
PACKAGE VERSION: 1.8.0
RECIPE NAME: github.com-influxdata-influxdb
LICENSE: MIT
Regards,
Robert
next prev parent reply other threads:[~2020-06-29 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 8:53 License reporting for golang (and rust) Irving ST
2020-06-24 20:46 ` [yocto] " Randy MacLeod
2020-06-29 21:32 ` Robert Berger [this message]
2020-06-30 11:37 ` Irving ST
2020-07-01 8:01 ` Robert Berger
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=4bafc350-fa80-c4e9-a13f-579484cc389e@gmail.com \
--to=robert.berger.yocto.user@gmail.com \
--cc=irving@ssfivy.com \
--cc=yocto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox