Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: 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 10:02:26 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1207101001080.2594@oneiric> (raw)
In-Reply-To: <1341927124.24837.8.camel@ted>

On Tue, 10 Jul 2012, Richard Purdie 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.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
> index 6ed1e6f..ffd59e9 100644
> --- a/meta/classes/sanity.bbclass
> +++ b/meta/classes/sanity.bbclass
> @@ -2,7 +2,7 @@
>  # Sanity check the users setup for common misconfigurations
>  #
>
> -SANITY_REQUIRED_UTILITIES ?= "patch diffstat texi2html makeinfo svn bzip2 tar gzip gawk chrpath wget cpio"
> +SANITY_REQUIRED_UTILITIES ?= "patch diffstat texi2html makeinfo git bzip2 tar gzip gawk chrpath wget cpio"
>
>  def raise_sanity_error(msg, d):
>      if d.getVar("SANITY_USE_EVENTS", True) == "1":
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 76ee65f..c94012e 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -152,6 +152,7 @@ DATETIME = "${DATE}${TIME}"
>  # its own in staging
>  ASSUME_PROVIDED = "\
>      bzip2-native \
> +    git-native \
>      grep-native \
>      diffstat-native \
>      patch-native \

  possibly a dumb question, but is this the sort of thing one could
extend in one's local.conf file if they were fairly sure their
installed versions were compatible?

rday

-- 

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

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




  reply	other threads:[~2012-07-10 14:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 13:32 bitbake.conf: Add git-native to ASSUME_PROVIDED Richard Purdie
2012-07-10 14:02 ` Robert P. J. Day [this message]
2012-07-10 14:09   ` Richard Purdie
2012-07-10 14:14     ` Robert P. J. Day
2012-07-10 15:00 ` McClintock Matthew-B29882
2012-07-10 15:57   ` Richard Purdie
2012-07-10 16:06     ` Burton, Ross
2012-07-10 16:11     ` McClintock Matthew-B29882
2012-07-10 18:35     ` Robert P. J. Day
2012-07-10 18:52       ` Khem Raj
2012-07-10 19:23         ` Richard Purdie
2012-07-10 19:58         ` Robert P. J. Day
2012-07-16 22:06   ` Colin Walters
2012-07-11 12:23 ` Enrico Scholz
2012-07-11 16:19   ` Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1207101001080.2594@oneiric \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox