All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Puhlman <jpuhlman@mvista.com>
To: openembedded-core@lists.openembedded.org
Cc: chris_larson@mentor.com
Subject: [PATCH] Add support for remote layering.
Date: Thu, 28 Apr 2011 11:09:38 -0700	[thread overview]
Message-ID: <1304014179-32612-1-git-send-email-jpuhlman@mvista.com> (raw)
In-Reply-To: <RFC: Layer tooling brainstorming>


> * Maybe need to split into "bootstrap" steps (e.g where pseduo is
   established, layers downloaded etc)

 So for the most part, the last product we shipped was largely arranged
in this manner. We were using collections, but in many cases layers is
just a reimplementation at a lower level(which is definitely goodness).
During ELC I had a number of discussions primarily around remote layer
fetch and most of the responses were meh, or that they wanted to make
the tool external to bitbake. So after the conference was over I went
ahead and worked out a version of the implementation  that could be done
either in a include or in the bitbake code itself. The version in the
git repo below is obviously just the bitbake implementation.

I have a rough implementation largely based off of collection.inc + some
enhancements we made internally for remote collection fetching. Some of
it is messy(setting up the early fetching vars with out using another
config), but for the ones I list in the patch header it appears to work
well.

I do not believe that this is complete, but it is probably a reasonable
starting point.

Pull URL: git://gitorious.org/jpwork/bb.git
Branch: remote-layering
Browse: https://gitorious.org/jpwork/bb/trees/remote-layering





       reply	other threads:[~2011-04-28 18:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <RFC: Layer tooling brainstorming>
2011-04-28 18:09 ` Jeremy Puhlman [this message]
2011-04-28 18:09 ` [PATCH] Add support for remote layering Jeremy Puhlman
2011-04-28 18:20   ` [PATCH 0/1] " Jeremy Puhlman
2011-05-06 13:15   ` [PATCH] " Richard Purdie
2011-05-12 13:11     ` Jeremy Puhlman
2011-05-12 17:34       ` Jeremy Puhlman
2011-05-20 16:45         ` Paul Eggleton
2011-05-20 17:42           ` Jeremy Puhlman
2011-07-01 13:24             ` Paul Eggleton
2011-07-01 17:17               ` Jeremy Puhlman
2011-07-01 18:43               ` Jeremy Puhlman
2011-07-01 21:37                 ` Richard Purdie
2011-07-02  0:33                   ` Jeremy Puhlman
2011-07-04 11:34                     ` Richard Purdie
2011-07-05 15:54                       ` Jeremy Puhlman
2011-07-04 12:39                     ` Paul Eggleton
2011-07-05 23:38                       ` Jeremy Puhlman
2011-07-11 17:46                         ` Paul Eggleton
2011-07-11 18:45                           ` Jeremy Puhlman
2011-07-18 15:59                           ` Paul Eggleton

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=1304014179-32612-1-git-send-email-jpuhlman@mvista.com \
    --to=jpuhlman@mvista.com \
    --cc=chris_larson@mentor.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.