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

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2012-07-10 at 11:52 -0700, Khem Raj wrote:
> On Tue, Jul 10, 2012 at 11:35 AM, Robert P. J. Day
> <rpjday@crashcourse.ca> wrote:
> >
> >   my opinion, which is mine, is to add a script someone can run that
> > tells them what appears to be safe to override from their current
> > distro.  that way, it's entirely optional and the developer deals with
> > the output at their own risk.
> 
> who determines the safeness ? thats what double QA RP mentioned is

If a script says its safe, the bug reports will come in about the script
being broken.

Most -native dependencies are either essential (perl, python, dbus,
autoconf, automake, libtool, gmp, mpc, mfpr) or trivial. The ones that I
really dislike are the ones that hold up the critical path of the build
(i.e. libc/toolchain).

git-native is now falling into this category. subversion-native used to
be an issue but is rapidly being consigned to the history books.

So bang for buck, git-native makes sense, most other -native
dependencies are required at this point. The only two I'd "safely" put
in an ASSUME_PROVIDED locally and off the top of my head are flex/bison
at this point and those are questionable with some known API gotchas.
We've even had problems with things like tar recently. Hard to believe
but true and we have the bug reports to prove it.

Cheers,

Richard