From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga02.intel.com ([134.134.136.20]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1UKXgW-00009b-IB for openembedded-core@lists.openembedded.org; Tue, 26 Mar 2013 18:29:31 +0100 Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 26 Mar 2013 10:12:19 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.84,913,1355126400"; d="scan'208";a="307691786" Received: from unknown (HELO helios.localnet) ([10.255.13.152]) by orsmga002.jf.intel.com with ESMTP; 26 Mar 2013 10:12:17 -0700 From: Paul Eggleton To: openembedded-core@lists.openembedded.org Date: Tue, 26 Mar 2013 17:12:16 +0000 Message-ID: <5482882.4phbAeRO1n@helios> Organization: Intel Corporation User-Agent: KMail/4.10.1 (Linux/3.5.0-26-generic; KDE/4.10.1; i686; ; ) In-Reply-To: References: MIME-Version: 1.0 Cc: qingtao.cao@windriver.com Subject: Re: [PATCH 1/1] rm_work.bbclass: inhibit rm_work per recipe X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 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, 26 Mar 2013 17:29:32 -0000 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Wednesday 13 March 2013 15:01:33 Qi.Chen@windriver.com wrote: > From: Chen Qi > > Use RM_WORK_WHITELIST to inhibit rm_work per recipe. In this way, > one can use rm_work for the most of the recipes but still keep the > work area for the recipe(s) one is working on. > > As an example, the following settings in local.conf will inhibit > rm_work for icu-native, icu and busybox. > INHERIT += "rm_work" > RM_WORK_WHITELIST += "icu-native icu busybox" > > If we comment out the RM_WORK_WHITELIST line and do a rebuild, the > working area of these recipes will be cleaned up. This is a great feature, but I just looked at it and realised that the term "whitelist" isn't really correct - this is more of a blacklist. The question is does it matter? If so we should probably change it now before it becomes too hard to change... Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre