From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [80.91.229.2] (helo=ciao.gmane.org) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1L5Lmq-0002PQ-GX for openembedded-devel@openembedded.org; Wed, 26 Nov 2008 15:54:40 +0100 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1L5Ljs-0001sm-Bv for openembedded-devel@openembedded.org; Wed, 26 Nov 2008 14:51:36 +0000 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 ; Wed, 26 Nov 2008 14:51:36 +0000 Received: from k.kooi by s55917625.adsl.wanadoo.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 26 Nov 2008 14:51:36 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: openembedded-devel@openembedded.org From: Koen Kooi Date: Wed, 26 Nov 2008 15:51:24 +0100 Message-ID: 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.5; en-US; rv:1.9.1b2pre) Gecko/20081120 Shredder/3.0b1pre Sender: news Subject: preferred-provider at the image level a.k.a why is all this fso stuff in my non-fso image 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: Wed, 26 Nov 2008 14:54:40 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi, Recently the FSO developers discovered that they can put RPROVIDES = "foo" RCONFLICTS = "foo" in their fso-foo recipe to have OE install fso-foo instead of foo in their fso-image. Great. The downside: people can't get 'foo' anymore in their image since 'fso-foo' will _always_ get choosen over 'foo'. Not so great. Normally it would be just a matter of putting PREFERRED_PROVIDER_foo = "foo" in the distro.conf, but that is not an option in this case, since when building 'fso-image' I actually want 'fso-foo' instead of 'foo' My proposal is: * remove the RPROVIDES, leave the RCONFLICTS * put 'fso-foo' in IMAGE_INSTALL in fso-images instead of 'foo' * educate people using RPROVIDES, RCONFLICTS and RREPLACES in recipes objections? regards, Koen