All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: paul.eggleton@linux.intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/4] insane.bbclass: add QA check: package-missing
Date: Tue, 23 Dec 2014 10:47:03 +0000	[thread overview]
Message-ID: <1419331623.1777.12.camel@linuxfoundation.org> (raw)
In-Reply-To: <cf0fb5e156cda7ef2fc1a6149432ae441efff2f7.1418293391.git.hongxu.jia@windriver.com>

On Thu, 2014-12-11 at 18:27 +0800, Hongxu Jia wrote:
> During packaging, check if there are any dependencies (RDEPENDS)
> on packages that have ended up empty and not produced; and if so
> produce an warn/error as soon as possible, instead of allowing
> the build to proceed up to do_rootfs and then the package manager
> reporting the package as missing.
> 
> At the moment, we use bb.persist_data as a global database to
> collect all available packages rdepends and rprovides. So in the
> do_package_qa task, while package not produced, we could compute
> rdepends chain, and report warn/error immediately.

I liked this until I saw you were using bb.persist_data. That isn't
under sstate control and will not result in deterministic builds.

Have you looked at the data saved by do_packageinfo into the pkgdata
structures? Can we not use the information on RDEPENDS and RPROVIDES
there instead?

Cheers,

Richard



  reply	other threads:[~2014-12-23 10:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 10:27 [PATCH 0/4] insane.bbclass: add QA check: package-missing Hongxu Jia
2014-12-11 10:27 ` [PATCH 1/4] " Hongxu Jia
2014-12-23 10:47   ` Richard Purdie [this message]
2014-12-11 10:27 ` [PATCH 2/4] perl_5.20.0: fix QA package-missing warnings Hongxu Jia
2014-12-11 10:27 ` [PATCH 3/4] linux-libc-headers.inc: " Hongxu Jia
2014-12-11 10:27 ` [PATCH 4/4] busybox.inc: " Hongxu Jia
2014-12-22  1:55 ` [PATCH 0/4] insane.bbclass: add QA check: package-missing Hongxu Jia
2014-12-25  1:48 [PATCH V2 " Hongxu Jia
2014-12-25  1:48 ` [PATCH 1/4] " Hongxu Jia

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=1419331623.1777.12.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=hongxu.jia@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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 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.