From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by mail.openembedded.org (Postfix) with ESMTP id 766AB6AFB5 for ; Thu, 18 Sep 2014 16:47:39 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.14.9/8.14.5) with ESMTP id s8IGlcr2016517 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Sep 2014 09:47:38 -0700 (PDT) Received: from [128.224.162.194] (128.224.162.194) by ALA-HCA.corp.ad.wrs.com (147.11.189.40) with Microsoft SMTP Server id 14.3.174.1; Thu, 18 Sep 2014 09:47:37 -0700 Message-ID: <541B0CA7.1040704@windriver.com> Date: Fri, 19 Sep 2014 00:47:35 +0800 From: Hongxu Jia User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Richard Purdie References: <1411048067.4736.8.camel@ted> In-Reply-To: <1411048067.4736.8.camel@ted> Cc: openembedded-core@lists.openembedded.org Subject: Re: [PATCH 1/3] sstatesig: Only dump incremental locked signatures X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2014 16:47:41 -0000 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit 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. > > 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. > > 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. Yes, you are right, it will overwrite, not for the locked sig file, but the core structure self.lockedsigs It could explain the necessary why I add 'type' to self.lockedsigs in previous path series. {pn:{task:{hash}}} --> {type:{pn:{task:{hash}}}} //Hongxu > > 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. > > Cheers, > > Richard