From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id EF2A777CF8 for ; Tue, 16 May 2017 13:14:53 +0000 (UTC) Received: from hex ([192.168.3.34]) (authenticated bits=0) by dan.rpsys.net (8.15.2/8.15.2/Debian-3) with ESMTPSA id v4GDEnDB001605 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 16 May 2017 14:14:50 +0100 Message-ID: <1494940489.27342.30.camel@linuxfoundation.org> From: Richard Purdie To: Peter Kjellerstedt , openembedded-core@lists.openembedded.org Date: Tue, 16 May 2017 14:14:49 +0100 In-Reply-To: References: X-Mailer: Evolution 3.18.5.2-0ubuntu3.1 Mime-Version: 1.0 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.11 (dan.rpsys.net [192.168.3.1]); Tue, 16 May 2017 14:14:50 +0100 (BST) X-Virus-Scanned: clamav-milter 0.99.2 at dan X-Virus-Status: Clean Subject: Re: [PATCH 0/2] Allow oe-pkgdata-util package-info to display more info 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: Tue, 16 May 2017 13:14:55 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Tue, 2017-05-16 at 12:56 +0200, Peter Kjellerstedt wrote: > After a build in our autobuilder, we use `oe-pkgdata-util package- > info > -f package.manifest` to store a file with information about each > installed package. This is typically used to compare builds later > on. Since not every difference to a package is explained by its > version, we have found it beneficial to also include the SRC_URI in > the generated file. > > This patch set adds SRC_URI to the pkgdata that is stored for each > package, and adds a new option to oe-pkgdata-util package-info, > -e , that can be used to display extra variables from the > pkgdata. I'm going to say no to this. The reason is that pkgdata is not really about collecting up all build information. If you want to know how two different builds differ, you'd use the sigdata files. If I take this patch, more will follow where you find some new difference you want to track and there are other mechanisms I'd suggest (buildhistory and siginfo for starters). I don't want to turn the pkgdata files into something they're not. Cheers, Richard