Re: bitbake.conf: Add git-native to ASSUME_PROVIDED

From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: bitbake.conf: Add git-native to ASSUME_PROVIDED
Date: Tue, 10 Jul 2012 16:57:29 +0100	[thread overview]
Message-ID: <1341935849.1294.2.camel@ted> (raw)
In-Reply-To: <CAEsOVNf0SDnxATQog_8Li1oeK6wkqhVH+m=Bt=L0bBbR02B05Q@mail.gmail.com>

On Tue, 2012-07-10 at 15:00 +0000, McClintock Matthew-B29882 wrote:
> On Tue, Jul 10, 2012 at 8:32 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Originally, git was something new, not installed everywhere and had commandline
> > stability problems. This has changed and git it no longer makes sense to
> > continually build this when the system installed version is likely sufficient.
> >
> > This speeds up build since recipes no longer have to wait for git-native to build
> > if they're fetched from a git:// SRC_URI.
> >
> > Also add git to the sanity checks and drop the no unneeded svn reference.
> 
> What about testing the host system for presence of certain things?
> Then one could
> 
> 1) yum/apt/etc install the needed items
> 
> or
> 
> 2) Build it if it's not present

Every time we put an if statement in like this, it basically means we
should double the amount of QA, one for one path and one for the other.

So whilst I've wondered about it, do we really need to do something like
this?

Cheers,

Richard