On Tue, 10 Jul 2012, Richard Purdie wrote:
> 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.pur...@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?
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.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
