From: Adriaan Schmidt <adriaan.schmidt@siemens.com>
To: <isar-users@googlegroups.com>
Cc: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Subject: [PATCH v2 3/3] docs(isar-sstate): update documentation of lint command
Date: Tue, 19 Jul 2022 14:35:09 +0200 [thread overview]
Message-ID: <20220719123509.308439-4-adriaan.schmidt@siemens.com> (raw)
In-Reply-To: <20220719123509.308439-1-adriaan.schmidt@siemens.com>
Signed-off-by: Adriaan Schmidt <adriaan.schmidt@siemens.com>
---
scripts/isar-sstate | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/scripts/isar-sstate b/scripts/isar-sstate
index 76bae544..3a1945e7 100755
--- a/scripts/isar-sstate
+++ b/scripts/isar-sstate
@@ -22,7 +22,7 @@ sstate cache:
`SSTATE_DIR`. To share them, you need to explicitly upload them to
the shared location, which is what isar-sstate is for.
-isar-sstate implements four commands (upload, clean, info, analyze),
+isar-sstate implements five commands (upload, clean, info, analyze, lint),
and supports three remote backends (filesystem, http/webdav, AWS S3).
## Commands
@@ -64,8 +64,10 @@ format as `bitbake-diffsigs`.
### lint
-The `lint` command searches form common flaws that reduce the
-cachability of a layer.
+The `lint` command searches for common flaws that reduce the cachability
+of a layer, e.g., signatures containing absolute paths from the host
+environment. Issues found this way usually indicate errors in recipes
+or in Isar itself.
## Backends
--
2.30.2
next prev parent reply other threads:[~2022-07-19 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 12:35 [PATCH v2 0/3] isar-sstate improvements Adriaan Schmidt
2022-07-19 12:35 ` [PATCH v2 1/3] fix(isar-sstate): catch errors during signature reading Adriaan Schmidt
2022-07-19 12:35 ` [PATCH v2 2/3] isar-sstate: refactor exit codes and error messages Adriaan Schmidt
2022-07-19 12:35 ` Adriaan Schmidt [this message]
2022-07-26 6:51 ` [PATCH v2 0/3] isar-sstate improvements Anton Mikanovich
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=20220719123509.308439-4-adriaan.schmidt@siemens.com \
--to=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.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