From: Jan-Simon Moeller <dl9pf@gmx.de>
To: Mikko.Rapeli@bmw.de
Cc: openembedded-core@lists.openembedded.org, jpew.hacker@gmail.com,
scott.murray@konsulko.com
Subject: Re: [OE-core] [PATCH v2] create-spdx: Get SPDX-License-Identifier from source
Date: Tue, 08 Feb 2022 14:56:46 +0100 [thread overview]
Message-ID: <2156423.DjyB96F3a6@monster> (raw)
In-Reply-To: <YgJxhJCQZLrkpgON@korppu>
Hi Mikko,
> I guess reports from both will be a superset of used licenses (and possibly
> copyright statements too) since the list of source files which are actually
> compiled is not known to these services.
Yes, the input is the 'bare' patched source archives. Yes, you're right. We do
only know the 'input' side of things aka all licenses of the source tree.
We do *not* know the 'output' side of things, yet. Aka what of these do end-up
in the image.
But IMHO let's raise the bar step by step.
> Currently the source recipes which have multiple licenses including
> problematic ones, are not cleaned up for license compliance scan. E.g.
> GPLv3 licensed source code are not deleted at do_patch() time. Thus reports
> need to be manually adjusted.
Well, thats a different topic and should be discussed alongside meta-gplv2.
Best,
JS
next prev parent reply other threads:[~2022-02-08 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 19:29 [PATCH v2] create-spdx: Get SPDX-License-Identifier from source Saul Wold
2022-02-07 20:33 ` [OE-core] " Scott Murray
2022-02-07 20:35 ` Joshua Watt
2022-02-07 20:59 ` Scott Murray
2022-02-08 12:50 ` Robert Berger
2022-02-08 13:19 ` Jan-Simon Moeller
2022-02-08 13:35 ` Mikko.Rapeli
2022-02-08 13:56 ` Jan-Simon Moeller [this message]
2022-02-08 14:16 ` Joshua Watt
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=2156423.DjyB96F3a6@monster \
--to=dl9pf@gmx.de \
--cc=Mikko.Rapeli@bmw.de \
--cc=jpew.hacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.murray@konsulko.com \
/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