From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1RGtf2-0008G2-1w for openembedded-core@lists.openembedded.org; Thu, 20 Oct 2011 16:32:00 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p9KEQ39i018566; Thu, 20 Oct 2011 15:26:03 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 17824-08; Thu, 20 Oct 2011 15:25:59 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p9KEPsNx018560 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Oct 2011 15:25:55 +0100 Message-ID: <1319120752.2410.34.camel@ted> From: Richard Purdie To: Patches and discussions about the oe-core layer Date: Thu, 20 Oct 2011 15:25:52 +0100 In-Reply-To: <4E9F5E5A.6040002@intel.com> References: <436a9b443962036ff35a5ffd86d80ad44350d5f2.1319012721.git.sgw@linux.intel.com> <758B37BA-B417-4B39-BF1C-0CEC613F067D@dominion.thruhere.net> <9DA5872FEF993D41B7173F58FCF6BE94E2F42EE2@orsmsx504.amr.corp.intel.com> <9DA5872FEF993D41B7173F58FCF6BE94E2F42F6A@orsmsx504.amr.corp.intel.com> <158EAB1C-0C40-4C5B-B47A-A4B8C90A2055@dominion.thruhere.net> <1319042998.22985.257.camel@phil-desktop> <4E9F018D.7030703@intel.com> <4E9F0CCF.3070404@intel.com> <4E9F5E5A.6040002@intel.com> X-Mailer: Evolution 3.2.1- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Cc: Phil Blundell Subject: Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer 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, 20 Oct 2011 14:32:00 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Wed, 2011-10-19 at 16:33 -0700, Saul Wold wrote: > On 10/19/2011 12:00 PM, Otavio Salvador wrote: > > On Wed, Oct 19, 2011 at 16:30, Khem Raj wrote: > > ... > >>>>> Many upstreams we can't track if updates are required automagically, so > >>>>> we > >>>>> need a place to record when the last manual check was, also possible > >>>>> reasons > >>>>> why we should not update to newer versions, ... > >> > >> hmm manual check means it has to be done manually is there any thing > >> that needs it ? > >> > >> I think unless they are distro specific which seems not since they are > >> in oe-core > >> they could exist in recipes thats my opinion. > > > > I agree that this should be put into the recipes. Besides this allows > > for checking if it was updated when the version has been updated. > > > > If done right, when updating the version this data will be updated > > together. I see no change in the amount of changes. > > > > A plus of this choice is it will be more difficult to forget to update > > that info. This happened in last qt update for an example. > > > > This may need to be something that the TSC brings up, possibly we can > talk about it in Prague next week. So just to give some background here, the information in those files was added by Yocto people to give some idea of the update status of various recipes. This included when the version was last checked/updated for recipes which we can't automate that process for, when certain cleanup checks were made, what the general state of the recipe was and who on the Yocto team was specifically looking after given recipes. When it was discussed, some of it was Yocto specific, some of it wasn't and popular opinion was against it going into the recipes themselves. I was ok with that given we have the pn- overrides and can handle the problem that way just fine. OE-Core happened and we kept the data with OE-Core at least for now. We have several options: a) Keep the data where it is b) Merge the data into the recipes c) Move the data out of OE-Core Since a lot of that data is fairly Yocto process specific, it may make sense to move it over to meta-yocto... Cheers, Richard