From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.cvg.de ([62.153.82.30]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1Sssoe-0004cL-NQ for openembedded-core@lists.openembedded.org; Sun, 22 Jul 2012 11:51:08 +0200 Received: from ensc-virt.intern.sigma-chemnitz.de (ensc-virt.intern.sigma-chemnitz.de [192.168.3.24]) by mail.cvg.de (8.14.4/8.14.4) with ESMTP id q6M9dbEh017552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 22 Jul 2012 11:39:38 +0200 Received: from ensc by ensc-virt.intern.sigma-chemnitz.de with local (Exim 4.76) (envelope-from ) id 1SssdV-0005tg-Hy for openembedded-core@lists.openembedded.org; Sun, 22 Jul 2012 11:39:37 +0200 From: Enrico Scholz To: openembedded-core@lists.openembedded.org References: <1342871746-14583-1-git-send-email-enrico.scholz@sigma-chemnitz.de> <1342946469.21788.54.camel@ted> Date: Sun, 22 Jul 2012 11:39:37 +0200 In-Reply-To: <1342946469.21788.54.camel@ted> (Richard Purdie's message of "Sun, 22 Jul 2012 09:41:09 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) MIME-Version: 1.0 Sender: Enrico Scholz X-DSPAM-Result: Innocent X-DSPAM-Probability: 0 X-DSPAM-Confidence: 0.99 X-Spam-Score: -5.2 X-Spam-Level: ----- X-Spam-Tests: AWL,BAYES_00,SPF_NEUTRAL,T_RP_MATCHES_RCVD,DSPAM_INNOCENT X-Scanned-By: MIMEDefang 2.73 Subject: Re: [PATCH] bitbake: do not set CCACHE_DISABLE=0 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: Sun, 22 Jul 2012 09:51:08 -0000 Content-Type: text/plain Richard Purdie writes: >> ccache checks for existence of environment; not for its value: >> ... >> Hence, avoid setting of $CCACHE_DISABLE instead of assigning '0'. > > Why doesn't CCACHE_DISABLE[unexport] = "1" help here? You mean, keeping the | export CCACHE_DISABLE ??= "${@[0,1][d.getVar('CCACHE', True) == '']}" and requesting explicitly that user specifies | CCACHE_DISABLE[unexport] = "1" in his .conf? Sounds hacky and inconsistent and makes it impossible to set CCACHE_DISABLE by external environment. > Doesn't the unexport flag stop this entering the environment? Perhaps. In the current bitbake, 'unexport' takes precedence over 'export'. But is this specified somewhere and will perhaps be changed in a later version. Enrico