Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jeremy Puhlman <jpuhlman@mvista.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Add support for remote layering.
Date: Fri, 1 Jul 2011 14:24:27 +0100	[thread overview]
Message-ID: <201107011424.27821.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <4DD6A817.6050701@mvista.com>

Hi Jeremy

Have looked at this further and I really think this needs to be a separate 
utility, but one still written in python using bitbake's infrastructure (like 
bitbake-layers). The advantages of this approach:

1) Avoids reworking bitbake's initialisation and avoids possible re-execution. 
A separate utility can take advantage of a full parse and utilise all of the 
user's configuration.

2) Fetching/updating layers should be (able to be) a conscious action rather 
than something that happens implicitly as part of the build process

I'm trying to put something together that does this at the moment, with a view 
to there being components that allow integration with the content tools you 
posted earlier. Will keep you posted.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-07-01 13:28 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 ` [PATCH] Add support for remote layering Jeremy Puhlman
2011-04-28 18:09 ` 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 [this message]
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=201107011424.27821.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=jpuhlman@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox