From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] default-distrovars.inc, task-core-boot.bb: Create distro overridable varibales
Date: Thu, 19 May 2011 01:47:28 +0100 [thread overview]
Message-ID: <1305766048.3424.385.camel@rex> (raw)
In-Reply-To: <CF837081-FAD3-4922-975B-B3CB6DD60533@dominion.thruhere.net>
On Wed, 2011-05-18 at 20:15 +0200, Koen Kooi wrote:
> Op 18 mei 2011, om 20:07 heeft Khem Raj het volgende geschreven:
> > there are certain common parts that can be abstracted
> > and can be maintained in oe-core so everyone benefits
> > from it and certain image specific parts can be done in
> > distros. So keeping common parts in core would still
> > be better IMO
>
> And in OE .dev we split task-boot from task-base to be able to get the
> benefits from task base without forcing task-boot. OE-core had the
> same till it got forcefully added to the extra depends last week.
Which was a genuine mistake and I need to merge the patch that is around
to address that particular issue.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-19 0:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 20:57 [PATCH 0/1] Define some distro overridable varibles Khem Raj
2011-05-17 20:57 ` [PATCH 1/1] default-distrovars.inc, task-core-boot.bb: Create distro overridable varibales Khem Raj
2011-05-17 21:03 ` Koen Kooi
2011-05-17 21:48 ` Khem Raj
2011-05-18 15:53 ` Phil Blundell
2011-05-18 16:40 ` Khem Raj
2011-05-18 17:08 ` Phil Blundell
2011-05-18 17:29 ` Koen Kooi
2011-05-18 17:52 ` Leon Woestenberg
2011-05-18 18:07 ` Khem Raj
2011-05-18 18:15 ` Koen Kooi
2011-05-19 0:47 ` Richard Purdie [this message]
2011-05-19 2:22 ` Khem Raj
2011-05-18 20:12 ` Phil Blundell
2011-05-18 20:16 ` Khem Raj
2011-05-18 19:22 ` Martin Jansa
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=1305766048.3424.385.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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