From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lo.gmane.org ([80.91.229.12]) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1NCTz7-0007z9-6A for openembedded-devel@lists.openembedded.org; Mon, 23 Nov 2009 09:09:24 +0100 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NCTxi-0003vJ-VF for openembedded-devel@lists.openembedded.org; Mon, 23 Nov 2009 09:07:54 +0100 Received: from s55917625.adsl.wanadoo.nl ([85.145.118.37]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 23 Nov 2009 09:07:54 +0100 Received: from k.kooi by s55917625.adsl.wanadoo.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 23 Nov 2009 09:07:54 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: openembedded-devel@lists.openembedded.org From: Koen Kooi Date: Mon, 23 Nov 2009 09:07:26 +0100 Message-ID: References: <20091115163618.GA3317@jama> <1258364356.5799.94.camel@dax.rpnet.com> <20091122190547.GC3349@jama> Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: s55917625.adsl.wanadoo.nl User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.6pre) Gecko/20091109 Shredder/3.0pre In-Reply-To: <20091122190547.GC3349@jama> Sender: news X-SA-Exim-Connect-IP: 80.91.229.12 X-SA-Exim-Mail-From: gcho-openembedded-devel@m.gmane.org X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: No (on linuxtogo.org); Unknown failure Subject: Re: SRCPV migration - How SRCPV works! X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2009 08:09:24 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 22-11-09 20:05, Martin Jansa wrote: > Every git recipe in OE tree should have some sane hash stored in > conf/distro/include/sane-srcrevs.inc The cabal decided that checksums are "part of the metadata" and belongs in the recipes. I don't understand why SRCREVs are so different. For SRCREVs my life would be a lot easier if all SRCREV where put in their respective recipes. Distros can always do SRCREV_pn-foo = "bar" PV_pn-foo = "1.2.3+gitr$SRCPV" in their distro.conf if needed. Due to scoping we do need some include for EFL_SRCREV, since those recipes are tightly tied together. > Kernel recipes are even more tricky, I bumped PE with SRCPV there too, > but Koen warned me later (thanks again) that there needs to be consistent PE > even between different recipes, because multiple machines can share same > kernel recipe and machine can pick between multiple recipes with highest > PV? Hmm now I don't understand what you mean with kernel recipes in this: > > > If something needs a PE bump, make sure you do it properly and bump PE > on the non scm fetched entries as well. For the kernel I wouldn't bump > PE, since too many machines can use different kernel recipes. > Basically: if you bump PE for one kernel recipe, you need to bump PE for all of them, so I guess it should be done in e.g. kernel.bbclass or linux.inc. Imagine I use a git kernel for 2.6.32rc6 and then add a recipe for 2.6.32, I'm fairly sure I'm going to forget to add PE in 2.6.32 the first time. > But be carefull with persistent cache file > something like this: > tmpdir-dev-shr/cache/om-gta02/bb_persist_data.sqlite So if I build pixman_git.bb for om-gta02 weekly, but monthly for beagleboard or om-gta01 I'll also get different numbers, right? I think the count should only be in a machine specific database if the SRC_URI/SRCREV is machine specific. regards, Koen