Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: [PATCH 0/1] linux-yocto: improve checkout error handling and reporting
Date: Thu, 23 Feb 2012 20:58:46 -0500	[thread overview]
Message-ID: <cover.1330048310.git.bruce.ashfield@windriver.com> (raw)

Richard/Saul,

I've got a long description in the patch itself that gives most of the
details of this change. But I'll hit some extra points here.

I've been cooking up this change for quite a while, since people seem to
be working with local repositories and it is a common mistake to point at
a non-bare linux-yocto repo. Due to the way the WORKDIR repo is created, this
can cause some really cryptic build errors. This change addresses that issue
and adds some workflow improvements at the same time.

  - it can optionally work with the 'bareclone' option in a SRC_URI. I sent
    that patch to bitbake-devel today. This isn't required, but if it is 
    used, a full bare clone is made in WORKDIR, and the checkout phase of
    linux-yocto detects that and creates local tracking branches for the 
    remotes. Mixes of local and remote branches work perfectly here.

  - it can also detect if a local, non-bare repository was the src repo.
    In this case, the tree is validated for the minimum branches that 
    make the rest of the build viable, and if they aren't found a clear
    message is dumped about the missing branches. No cryptic errors from
    the build.

  - instead of poking at git internals to create the local branches in 
    WORKDIR. real tracking branches are created. With this, you now have
    the ability to work on your repository and push changes to your 
    upstream, or fetch changes into the remotes and then bring them into
    your local branches. Everthing is setup properly for a more 'normal'
    development workflow.

I wanted to send this out before I send my -stable updates to the repos
themselves.

Cheers,

Bruce

The following changes since commit d8b3718303c3d56394c722059f1a73bd79131d0a:

  texi2html: Fix for multilib (2012-02-22 23:03:16 +0000)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (1):
  linux-yocto: improve checkout error handling and reporting

 meta/classes/kernel-yocto.bbclass |   72 +++++++++++++++++++++++++------------
 1 files changed, 49 insertions(+), 23 deletions(-)

-- 
1.7.4.1




             reply	other threads:[~2012-02-24  2:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24  1:58 Bruce Ashfield [this message]
2012-02-24  1:58 ` [PATCH 1/1] linux-yocto: improve checkout error handling and reporting Bruce Ashfield

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=cover.1330048310.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@intel.com \
    /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