From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (dan.rpsys.net [93.97.175.187]) by mx1.pokylinux.org (Postfix) with ESMTP id 408D64C81021 for ; Fri, 17 Dec 2010 08:01:26 -0600 (CST) 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 oBHE0QXW025959; Fri, 17 Dec 2010 14:00:26 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 LOiimhFttDaZ; Fri, 17 Dec 2010 14:00:26 +0000 (GMT) Received: from [192.168.1.42] (tim [93.97.173.237]) (authenticated bits=0) by dan.rpsys.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id oBHE0MXK025956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 17 Dec 2010 14:00:24 GMT From: Richard Purdie To: Chris Larson In-Reply-To: References: <4D0ABF1C.6090706@intel.com> <625BA99ED14B2D499DC4E29D8138F1504D5F40984C@shsmsx502.ccr.corp.intel.com> <4D0AC7D8.8080001@intel.com> <625BA99ED14B2D499DC4E29D8138F1504D5F409868@shsmsx502.ccr.corp.intel.com> <4D0ACB43.8050909@intel.com> <625BA99ED14B2D499DC4E29D8138F1504D5F409997@shsmsx502.ccr.corp.intel.com> <625BA99ED14B2D499DC4E29D8138F1504D5F4099DD@shsmsx502.ccr.corp.intel.com> Date: Fri, 17 Dec 2010 13:58:49 +0000 Message-ID: <1292594329.25087.40.camel@rex> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Cc: "paul.eggleton@linux.intel.com" , "poky@pokylinux.org" Subject: Re: perl binary hard-code path hurts sstate X-BeenThere: poky@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Poky build system developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Dec 2010 14:01:26 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Fri, 2010-12-17 at 06:49 -0700, Chris Larson wrote: > These sorts of issues aren't new, or fun, sadly. We've run into many > like this using packaged staging. We had to use the variable to > disable packaged-staging for exactly this reason, so something similar > for sstate would indeed be useful for this. In cases like this I'd suggest adding the encoded path into the checksum via vardeps. This means the sstate package will be reused when the path matches but not otherwise. We can then work on removing the dependencies which I agree is the goal but we should get them identified first. Cheers, Richard