From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Paul Eggleton <paul.eggleton@linux.microsoft.com>,
"docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Subject: RE: [docs] [PATCH 7/9] ref-manual: add empty-dirs QA check and QA_EMPTY_DIRS*
Date: Fri, 22 Apr 2022 09:50:16 +0000 [thread overview]
Message-ID: <9d1b317395dd4adabf7f04726b4f9fc9@axis.com> (raw)
In-Reply-To: <0fb99813b129f7239e08240d22397a50c53ed883.1650591341.git.paul.eggleton@linux.microsoft.com>
> -----Original Message-----
> From: docs@lists.yoctoproject.org <docs@lists.yoctoproject.org> On Behalf
> Of Paul Eggleton
> Sent: den 22 april 2022 03:41
> To: docs@lists.yoctoproject.org
> Subject: [docs] [PATCH 7/9] ref-manual: add empty-dirs QA check and
> QA_EMPTY_DIRS*
>
> From: Paul Eggleton <paul.eggleton@microsoft.com>
>
> This check is new in kirkstone.
>
> Signed-off-by: Paul Eggleton <paul.eggleton@microsoft.com>
> ---
> documentation/ref-manual/classes.rst | 5 +++++
> documentation/ref-manual/qa-checks.rst | 10 +++++++++-
> documentation/ref-manual/variables.rst | 15 +++++++++++++++
> 3 files changed, 29 insertions(+), 1 deletion(-)
>
> diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
> index 13cc2bb..a084ace 100644
> --- a/documentation/ref-manual/classes.rst
> +++ b/documentation/ref-manual/classes.rst
> @@ -1039,6 +1039,11 @@ Here are the tests you can list with the :term:`WARN_QA` and
> cases, such as dynamically loaded modules, these symlinks
> are needed instead in the main package.
>
> +- ``empty-dirs:`` Checks that packages are not installing files to
> + directories that are normally expected to be empty (such as ``/tmp``)
> + The list of directories that are checked is specified by the
> + :term:`QA_EMPTY_DIRS` variable.
> +
> - ``file-rdeps:`` Checks that file-level dependencies identified by
> the OpenEmbedded build system at packaging time are satisfied. For
> example, a shell script might start with the line ``#!/bin/bash``.
> diff --git a/documentation/ref-manual/qa-checks.rst b/documentation/ref-manual/qa-checks.rst
> index 3364311..e881697 100644
> --- a/documentation/ref-manual/qa-checks.rst
> +++ b/documentation/ref-manual/qa-checks.rst
> @@ -154,7 +154,15 @@ Errors and Warnings
> ``FILES:${PN}-dbg``. See :term:`FILES` for additional
> information on :term:`FILES`.
>
> -
> +.. _qa-check-empty-dirs:
> +
> +- ``<packagename> installs files in <path>, but it is expected to be empty [empty-dirs]``
> +
> + The specified package is installing files into a directory that is
> + normally expected to be empty (such as ``/tmp``). These files may
> + be more appropriately installed to a different location, or
> + perhaps alternatively not installed at all.
> +
> .. _qa-check-arch:
>
> - ``Architecture did not match (<file_arch>, expected <machine_arch>) in <file> [arch]``
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 4803578..47c8a8f 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -6084,6 +6084,21 @@ system and gives an overview of their function and contents.
> In the previous example,
> the version of the dependency is :term:`PYTHON_PN`.
>
> + :term:`QA_EMPTY_DIRS`
> + Specifies a list of directories that are expected to be empty when
> + packaging; if ``empty-dirs`` appears in :term:`ERROR_QA` or
> + :term:`WARN_QA` these will be checked and an error or warning
> + (respectively) will be produced.
> +
> + The default :term:`QA_EMPTY_DIRS` value is set in
> + :ref:`classes/insane.bbclass <ref-classes-insane>`.
> +
> + :term:`QA_EMPTY_DIRS_RECOMMENDATION`
> + Specifies a recommendation for a directory why it must be empty,
> + which will be included in the error message if a specific directory
> + is found to contain files. Must be overridden with the directory
> + path to match on.
Add:
If no recommendation is specified for a directory, then the default
"but it is expected to be empty" will be used.
Example:
QA_EMPTY_DIRS_RECOMMENDATION:/dev = "but all devices must be created at runtime"
(Please add formatting for the example, I don't know rst enough.)
> +
> :term:`RANLIB`
> The minimal command and arguments to run ``ranlib``.
>
> --
> 1.8.3.1
//Peter
next prev parent reply other threads:[~2022-04-22 16:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 1:40 [PATCH 0/9] Release documentation for 4.0 Paul Eggleton
2022-04-22 1:40 ` [PATCH 1/9] migration-3.4: add missing entry on EXTRA_USERS_PARAMS Paul Eggleton
2022-04-22 10:30 ` [docs] " Quentin Schulz
2022-04-22 10:41 ` Richard Purdie
2022-04-22 1:40 ` [PATCH 2/9] ref-manual: add a note about hard-coded passwords Paul Eggleton
2022-04-22 9:35 ` [docs] " Peter Kjellerstedt
2022-04-22 1:40 ` [PATCH 3/9] ref-manual: mention wildcarding support in INCOMPATIBLE_LICENSE Paul Eggleton
2022-04-22 9:37 ` [docs] " Peter Kjellerstedt
2022-04-22 1:40 ` [PATCH 4/9] ref-manual: add mention of vendor filtering to CVE_PRODUCT Paul Eggleton
2022-04-22 1:40 ` [PATCH 5/9] ref-manual: add KERNEL_DEBUG_TIMESTAMPS Paul Eggleton
2022-04-22 1:40 ` [PATCH 6/9] ref-manual: add XZ_THREADS and ZSTD_THREADS Paul Eggleton
2022-04-22 10:40 ` [docs] " Quentin Schulz
2022-04-22 11:46 ` Richard Purdie
2022-04-22 12:47 ` Quentin Schulz
2022-04-22 12:50 ` Richard Purdie
2022-04-22 1:40 ` [PATCH 7/9] ref-manual: add empty-dirs QA check and QA_EMPTY_DIRS* Paul Eggleton
2022-04-22 9:50 ` Peter Kjellerstedt [this message]
2022-04-22 10:51 ` [docs] " Quentin Schulz
2022-04-22 1:40 ` [PATCH 8/9] migration-guides: complete migration guide for 4.0 Paul Eggleton
2022-04-22 11:10 ` [docs] " Quentin Schulz
2022-04-22 12:09 ` Richard Purdie
2022-04-22 1:40 ` [PATCH 9/9] migration-guides: add release notes " Paul Eggleton
2022-04-22 11:17 ` [docs] " Quentin Schulz
2022-04-22 11:18 ` [docs] [PATCH 0/9] Release documentation " Quentin Schulz
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=9d1b317395dd4adabf7f04726b4f9fc9@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=docs@lists.yoctoproject.org \
--cc=paul.eggleton@linux.microsoft.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