From: Jeremy Puhlman <jpuhlman@mvista.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: "paul.eggleton@linux.intel.com >> Paul Eggleton"
<paul.eggleton@linux.intel.com>,
chris_larson@mentor.com
Subject: Re: [PATCH] Add support for remote layering.
Date: Thu, 12 May 2011 10:34:03 -0700 [thread overview]
Message-ID: <4DCC1A0B.3040802@mvista.com> (raw)
In-Reply-To: <4DCBDC96.1080306@mvista.com>
> So currently it gets stashed in the locations specified above. Currently
> the code has the ability to extract values out of the uri as new bits.
> The above would be reasonable, but you could do as well:
>
> BBLAYERS = " \
>> http://url.to.my.tarball/tarball.tar.gz;local=/path/to/layer \
>> git://gitserver.com/git/repo;proto=httplocalLayer=/path/to/layer/two \
>> /path/to/layer/three \
>> /path/to/layer/four \
>
> With the current implementation the above is fairly straight forward.
> (not that I am implying implementation should necessarily dictate the
> what is done, just noting the above is significantly easier to implement
> from the point the code is now.)
Arg. Too early this morning. That should have been something like:
> BBLAYERS = " \
>> http://url.to.my.tarball/tarball.tar.gz;localLayer=/path/to/layer \
>> git://gitserver.com/git/repo;proto=http;localLayer=/path/to/layer/two \
>> /path/to/layer/three \
>> /path/to/layer/four \
>
or something to that effect.
next prev parent reply other threads:[~2011-05-12 17:37 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 [this message]
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=4DCC1A0B.3040802@mvista.com \
--to=jpuhlman@mvista.com \
--cc=chris_larson@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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