Return-Path: Received: from tim.rpsys.net (93-97-173-237.zone5.bethere.co.uk [93.97.173.237]) by mx1.pokylinux.org (Postfix) with ESMTP id F2CFC4C800BE for ; Mon, 14 Mar 2011 12:55:44 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p2EHteA6004711; Mon, 14 Mar 2011 17:55:40 GMT Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 04524-03; Mon, 14 Mar 2011 17:55:36 +0000 (GMT) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p2EHtWcR004705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Mar 2011 17:55:33 GMT From: Richard Purdie To: Tom Rini In-Reply-To: <4D7E547A.5020906@mentor.com> References: <4D7A08BF.80303@mlbassoc.com> <1299863594.1445.2875.camel@rex> <4D7A59DC.6070900@mlbassoc.com> <4D7A5AFA.7080107@mentor.com> <4D7A5CB8.8000701@mlbassoc.com> <20110312001053.GF5603@sakrah.homelinux.org> <4D7E4FB9.2060203@mentor.com> <1300124421.30423.311.camel@rex> <4D7E547A.5020906@mentor.com> Date: Mon, 14 Mar 2011 17:55:26 +0000 Message-ID: <1300125326.30423.343.camel@rex> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 X-Virus-Scanned: amavisd-new at rpsys.net Cc: poky@yoctoproject.org Subject: Re: Native vs not 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: Mon, 14 Mar 2011 17:55:45 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Mon, 2011-03-14 at 10:46 -0700, Tom Rini wrote: > On 03/14/2011 10:40 AM, Richard Purdie wrote: > > On Mon, 2011-03-14 at 10:26 -0700, Tom Rini wrote: > >> On 03/11/2011 05:10 PM, Khem Raj wrote: > >> > >>> I think having some buildhost/native packages (based on distro/version) trusted and assume provided or even > >>> installed using the build host package management could be one approach > >>> in modern distros I think we could use lot of host packages as is. or > >>> may be trust all and keep a list of blacklisted packages for a given > >>> distro might be something useful > >> > >> I've been thinking about this a bit and at least at the high level there > >> is an argument for making it easy to opt out of a big class of host > >> tools, on a modern distro and trade reprodicibility / reliability for > >> faster initial build times. And on the flip side, opt out of a bit more > >> of our host tool dependencies. > > > > This is what ASSUME_PROVIDED is there for :) > > Well yes. But it'd be nice if we had a few helpers so you could say: > ASSUME_PROVIDED += "${SCM_FETCH_TOOLS} ${DOCUMENTATION_GENERATION_TOOLS} > ..." > and so forth. We need to user to be very clearly aware of what they're adding IMO so I'd prefer maybe just some commented out lines such as: # Uncomment this if you want to use the system provided scm utilities # instead of having the system build them #ASSUME_PROVIDED += "git-native svn-native" I'm actually thinking about a local.conf.sample.advanced file where we list a load of things like this. This means we can keep local.conf.sample simple (the things they probably *need* to look at) yet still show users some of the other more advanced options. Cheers, Richard