[yocto] under what circumstances is BBCLASSEXTEND = "native" required in a recipe?

[Robert P. J. Day]

On Sat, 11 Aug 2012, Chris Larson wrote:

> On Sat, Aug 11, 2012 at 11:32 AM, Robert P. J. Day
> <rpjday at crashcourse.ca> wrote:

> > p.s.  as a more obvious example, consider "git".  it's now
> > "ASSUME_PROVIDED", and listed in the quick start guide as required
> > on the dev host, but it also still supports a native build.  i'm
> > just trying to clarify that, in cases like that, supporting the
> > -native build is no longer necessary.  or am i missing something?

> Supporting it isn't necessary, this is true, but we do want to
> remove as many hard host dependencies as possible over time, no?

  we do?  since when?  not being facetious, but wondering if this is
an actual, codified goal, since it seems fly in the face of the recent
addition of "git-native" to ASSUME_PROVIDED.  what was the point of
that, if not to remove the burden of providing "git" from OE and
dumping it in the lap of the developer?

> Perhaps the bbclassextend only exists to prepare for such a point.
> Also, having a -native available doesn't *harm* anything. At most it
> slightly increases ram usage up front when it produces the second
> variation of the recipe.

  yup, i agree, i'm just trying to understand the philosophy here.

rday

p.s.  i'm still wondering if there's a convenient way to identify
utilities on the dev host that are candidates for ASSUME_PROVIDED.
surely a relatively recent version of subversion would be adequate,
but how would one actually *know* that?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================