From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dan.rpsys.net ([93.97.175.187]) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1N9zF0-0006VR-0J for openembedded-devel@lists.openembedded.org; Mon, 16 Nov 2009 11:55:29 +0100 Received: from localhost (dan.rpsys.net [127.0.0.1]) by dan.rpsys.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id nAGAotiT008311 for ; Mon, 16 Nov 2009 10:50:55 GMT X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id R-JfY2icuTv2 for ; Mon, 16 Nov 2009 10:50:54 +0000 (GMT) Received: from [192.168.1.3] (tim [93.97.173.237]) (authenticated bits=0) by dan.rpsys.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id nAGAoqIo008297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 16 Nov 2009 10:50:53 GMT From: Richard Purdie To: openembedded-devel@lists.openembedded.org In-Reply-To: References: <20091115163618.GA3317@jama> <1258364356.5799.94.camel@dax.rpnet.com> Date: Mon, 16 Nov 2009 10:49:30 +0000 Message-Id: <1258368570.5799.99.camel@dax.rpnet.com> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 X-SA-Exim-Connect-IP: 93.97.175.187 X-SA-Exim-Mail-From: rpurdie@rpsys.net 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 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, 16 Nov 2009 10:55:29 -0000 Content-Type: text/plain Content-Transfer-Encoding: 7bit On Mon, 2009-11-16 at 11:37 +0100, Koen Kooi wrote: > So basically every recipe that is using SRCPV in PV or PR is unsuitable > to be put in online feeds. That should be enough to stop the SRCPV merge > into .dev. How is this different to the current situation though? If SRCREV is locked down you will get 1 as the local build revision back and it will not change and will be the same for everyone. If its not locked down, all bets are off but they always have been - no change. Cheers, Richard