Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Machine dependencies validation with sstate
Date: Fri, 03 Feb 2012 16:46:51 +0000	[thread overview]
Message-ID: <1328287611.16474.3.camel@ted> (raw)
In-Reply-To: <CAEsOVNdz1iFgoBa6MsanDUEgQym3-EbaBZy_rJ=om5_oYMvG4g@mail.gmail.com>

On Mon, 2012-01-30 at 16:48 +0000, McClintock Matthew-B29882 wrote:
> Have you found an easy way to traverse up a dependency chain to the
> initial signature? It can take a while running the above command until
> you get to the *real* signature change on not just a signature change
> because one of the dependencies signature changed...
> 
> Some sort of tool at this point seems to be the solution. It could do
> a lot more as well. Tracking signature changes between builds would be
> nice as well. The list could go on and on...

There isn't an easy way at the moment, I've just been relying on an
educated guess from looking at two sets of files where the differences
appear to start from.

I agree we really need a tool in this kind of area. You could file an
enhancement request but it could really do with someone working on it to
help drive it forward. The bitbake core code at least already has many
useful functions to help perform the analysis.

Cheers,

Richard




  reply	other threads:[~2012-02-03 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 17:22 Machine dependencies validation with sstate Richard Purdie
2012-01-30 16:48 ` McClintock Matthew-B29882
2012-02-03 16:46   ` Richard Purdie [this message]
2012-02-16 13:44 ` Martin Jansa
2012-02-16 13:54   ` Martin Jansa
2012-02-16 14:22   ` Martin Jansa
2012-02-22 13:05   ` Martin Jansa

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=1328287611.16474.3.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=B29882@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox