From: Nicky Chorley <ndchorley@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Nicky Chorley <ndchorley@gmail.com>, linux-spdx@vger.kernel.org
Subject: Re: Fwd: scripts/spdxcheck.py's third-party dependencies
Date: Fri, 6 Aug 2021 07:44:41 +0100 (BST) [thread overview]
Message-ID: <42bfb9dc-3bbf-eba6-d1e9-ae56bc49f94@rigel.lan> (raw)
In-Reply-To: <YQvX4u/H8cV1pAPu@kroah.com>
On Thu, 5 Aug 2021, Greg KH wrote:
> But we do not use pip to do kernel builds, so what is this going to help
> with?
It's just about making people's lives easier for running the spdxcheck.py
script - not everyone will have the third-party libraries installed, so
listing them means they can be installed easily. For example:
diff --git a/scripts/README.spdxcheck b/scripts/README.spdxcheck
new file mode 100644
index 000000000000..80bb6308e5c5
--- /dev/null
+++ b/scripts/README.spdxcheck
@@ -0,0 +1,6 @@
+The script spdxcheck.py requires installation of some third party
+libraries. These are listed in ``requirements-spdxcheck.txt`` and can
+be installed with
+
+``pip install -r requirements-spdxcheck.txt``
+
diff --git a/scripts/requirements-spdxcheck.txt b/scripts/requirements-spdxcheck.txt
new file mode 100644
index 000000000000..9a4633040897
--- /dev/null
+++ b/scripts/requirements-spdxcheck.txt
@@ -0,0 +1,3 @@
+ply
+GitPython
+
I'll reformat as a proper patch with any changes if this is useful.
Best,
Nicky
next prev parent reply other threads:[~2021-08-06 6:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <efcdf26-fd74-3d7d-25b1-d77ed3c493@rigel.lan>
2021-07-27 6:42 ` Fwd: scripts/spdxcheck.py's third-party dependencies Nicky Chorley
2021-07-27 6:47 ` Greg KH
2021-07-31 11:57 ` Nicky Chorley
2021-08-05 12:21 ` Greg KH
2021-08-06 6:44 ` Nicky Chorley [this message]
2021-08-10 11:27 ` Zavras, Alexios
2021-08-10 16:57 ` Christoph Hellwig
2021-08-10 21:00 ` Thomas Gleixner
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=42bfb9dc-3bbf-eba6-d1e9-ae56bc49f94@rigel.lan \
--to=ndchorley@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-spdx@vger.kernel.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