All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: "Mittal, Anuj" <anuj.mittal@intel.com>
Cc: "OE Core (openembedded-core@lists.openembedded.org)"
	<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [honister][PATCH] insane.bbclass: Add a check for directories that are expected to be empty
Date: Thu, 11 Nov 2021 09:42:28 +0000	[thread overview]
Message-ID: <d62d07f792e4450c981095d86eee280c@axis.com> (raw)
In-Reply-To: <0acd0e851fab2cbbc1580ec45b1765d5c22e26b5.camel@intel.com>

> -----Original Message-----
> From: Mittal, Anuj <anuj.mittal@intel.com>
> Sent: den 11 november 2021 04:06
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Subject: Re: [OE-core] [honister][PATCH] insane.bbclass: Add a check for
> directories that are expected to be empty
> 
> On Wed, 2021-11-10 at 20:53 +0000, Peter Kjellerstedt wrote:
> > > -----Original Message-----
> > > From: openembedded-core@lists.openembedded.org <openembedded-
> > > core@lists.openembedded.org> On Behalf Of Anuj Mittal
> > > Sent: den 9 november 2021 15:36
> > > To: openembedded-core@lists.openembedded.org; Peter Kjellerstedt
> > > <peter.kjellerstedt@axis.com>
> > > Subject: Re: [OE-core] [honister][PATCH] insane.bbclass: Add a
> > > check for
> > > directories that are expected to be empty
> > >
> > > On Mon, 2021-11-08 at 18:10 +0100, Peter Kjellerstedt wrote:
> > > > From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> > > >
> > > > The empty-dirs QA check verifies that all directories specified
> > > > in
> > > > QA_EMPTY_DIRS are empty. It is possible to specify why a
> > > > directory is
> > > > expected to be empty by defining
> > > > QA_EMPTY_DIRS_RECOMMENDATION:<path>,
> > > > which will then be included in the error message if the directory
> > > > is
> > > > not empty. If it is not specified for a directory, then "but it
> > > > is
> > > > expected to be empty" will be used.
> > > >
> > > > Change-Id: Ic61019528f4b22f26e42e78125a99666ae27c7f5
> > > > Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> > > > ---
> > > >
> > > > Compared to the corresponding patch for master, there are two
> > > > differences:
> > > >
> > > > * "/var/volatile" is not added to QA_EMPTY_DIRS by default.
> > > > * "empty-dirs" is added to WARN_QA instead of ERROR_QA.
> > > >
> > > > This should make it safe to add this QA test to Honister without
> > > > introdusing any new QA errors, while still allowing the QA test to be
> > > > activated for those who wants to use it.
> > >
> > > Does it have to be enabled by default?
> >
> > Well, it doesn't have to be enabled. However, without /var/volatile in
> > QA_EMPTY_DIRS, there should be no warnings generated for OE-Core or
> > OpenEmbedded so it should not hurt to have it in WARN_QA.
> 
> Right, but there could be unexpected warnings for other downstream
> layers in release versions.

True, but they would still just be warnings.

> I think we can add the test but only for people to use it if they'd
> like to.

Sure, if you prefer that. Do you want me to send an updated patch, or will 
you take care of it?

> Thanks,
> 
> Anuj

//Peter

  parent reply	other threads:[~2021-11-11  9:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 17:10 [honister][PATCH] insane.bbclass: Add a check for directories that are expected to be empty Peter Kjellerstedt
2021-11-09 14:36 ` [OE-core] " Mittal, Anuj
     [not found]   ` <bd35b97c54314581be874f9bd8adcf83@axis.com>
     [not found]     ` <0acd0e851fab2cbbc1580ec45b1765d5c22e26b5.camel@intel.com>
2021-11-11  9:42       ` Peter Kjellerstedt [this message]
2021-11-11 10:30         ` Richard Purdie
2021-11-11 11:02           ` Peter Kjellerstedt
2021-11-12  2:52         ` Mittal, Anuj

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=d62d07f792e4450c981095d86eee280c@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=anuj.mittal@intel.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.