On Tuesday 18 March 2014 09:52:23 Chris Larson wrote:
> On Tue, Mar 18, 2014 at 7:38 AM, Chris Larson wrote:
> > On Tue, Mar 18, 2014 at 6:48 AM, Paul Eggleton <
> > paul.eggle...@linux.intel.com> wrote:
> >> FWIW, this broke builds on my CentOS build machine that uses a slightly
> >> older
> >> b
On Tue, Mar 18, 2014 at 7:38 AM, Chris Larson wrote:
>
> On Tue, Mar 18, 2014 at 6:48 AM, Paul Eggleton <
> paul.eggle...@linux.intel.com> wrote:
>
>> On Friday 14 March 2014 19:06:26 Christopher Larson wrote:
>> > This will let folks extend the oe package with modules from other
>> layers.
>> >
On Tue, Mar 18, 2014 at 6:48 AM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:
> On Friday 14 March 2014 19:06:26 Christopher Larson wrote:
> > This will let folks extend the oe package with modules from other layers.
> > Given openembedded consists of more than just oe-core, I think this
On Friday 14 March 2014 19:06:26 Christopher Larson wrote:
> This will let folks extend the oe package with modules from other layers.
> Given openembedded consists of more than just oe-core, I think this makes
> sense, and adds some useful flexibility.
>
> Signed-off-by: Christopher Larson
> ---
This will let folks extend the oe package with modules from other layers.
Given openembedded consists of more than just oe-core, I think this makes
sense, and adds some useful flexibility.
Signed-off-by: Christopher Larson
---
meta/lib/oe/__init__.py | 2 ++
1 file changed, 2 insertions(+)
diff
