Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] sstatesig: Only dump incremental locked signatures
Date: Thu, 18 Sep 2014 23:10:39 +0800	[thread overview]
Message-ID: <541AF5EF.3050904@windriver.com> (raw)
In-Reply-To: <1411048067.4736.8.camel@ted>

On 09/18/2014 09:47 PM, Richard Purdie wrote:
> I'm afraid I'm starting to feel very strongly this is not a direction we
> should move in. Having the ability to write out a .inc file containing
> on a delta is one thing, writing out a file for automatic inclusion and
> trying to maintain that file is not something I feel comfortable with.

Yes, I understand that your worry is reasonable, so many unexpected
exception needs to be maintained

> I think that at some point there needs to be external tooling handling
> the inclusion and updating of this file and that the sigs code is not
> the place for this.

I once coded a python script to handling the locked sig file from an
existed sstate, translated sstate item name (ends with '.tgz.siginfo')
to "<pn>:<task>:<hash>" tuple.

The main blocker is: for some tasks (such as do_patch/do_fetch/
do_unpack), the target and native have the same pn in sstate, such as:
''sstate-cache/c6/sstate:automake::1.14.1:r0::3:c667b87f5d4e15198afc744f525895fc_unpack.tgz.siginfo"
is used for "automake" and "automake-native", you could not figure
out arch (which used as type in locked sig file) from it neither.

> For example, consider the case where you switch machines and want to
> share an include file between these machines. With the changes proposed
> in this patch series it will simply overwrite the file and remove the
> entries for the other machine.

I think the swith machines case could work in this patch series,
It appends to the tail of the locked sig file, and not overwrite
the other machine's sig if incremetnal dump is set.

But I indeed understand what you worry about.

> We could keep trying to patch up this code to cover every combination
> and eventuality but in the end, I believe the maintenance of this file
> should be something external, the sigs code should only be concerned
> with the generation of the core entries.

Completely agree.

//Hongxu

> Cheers,
>
> Richard



  parent reply	other threads:[~2014-09-18 15:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18  7:23 [PATCH V3 0/3] sstatesig: add support to dump incremental locked signatures Hongxu Jia
2014-09-18  7:23 ` [PATCH 1/3] sstatesig: Only " Hongxu Jia
2014-09-18 13:47   ` Richard Purdie
2014-09-18 13:56     ` Mark Hatle
2014-09-18 15:10     ` Hongxu Jia [this message]
2014-09-18 16:47     ` Hongxu Jia
2014-09-18  7:23 ` [PATCH 2/3] sstatesig: add new item checking for locked signature dump Hongxu Jia
2014-09-18  7:23 ` [PATCH 3/3] sstatesig: fix to support unincremental " 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=541AF5EF.3050904@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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