From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: oe-core cleanup...
Date: Wed, 2 Mar 2011 12:33:47 -0600 [thread overview]
Message-ID: <4D6E8D8B.7030906@windriver.com> (raw)
In-Reply-To: <BED5DD21-1E73-4DB2-9E29-17E70DF7344C@dominion.thruhere.net>
On 3/2/11 12:27 PM, Koen Kooi wrote:
>
> Op 2 mrt 2011, om 19:00 heeft Richard Purdie het volgende geschreven:
>
>> Thanks for starting this thread Mark, I've also just been looking at
>> this question so its timely.
>>
>> On Wed, 2011-03-02 at 11:30 -0600, Mark Hatle wrote:
>>> I finally got a chance to look at the oe-core and where it currently is.. Some
>>> suggestions below:
>>>
>>> LICENSE file, this may need to be cleaned up to only cover the components
>>> actually in the oe-core.
>>>
>>> README likely needs some revision
>>>
>>> README.hardware needs a lot of revision. Anything outside of support for QEMU
>>> should be removed.
>>>
>>> The meta-demoapps and meta-rt components, will those be staying or going?
>>>
>>> The meta/recipes.txt needs to be verified as still what we want -- I assume it
>>> is at this point..
>>>
>>> meta/recipes-... sato, qt, gnome, I thought were going elsewhere?
>>>
>>> Do the items in the "scripts" need to be renamed or is Poky being kept in the
>>> naming? Same with the poky-init-build-env?
>>>
>>> Then I also assume the items in the documentation directory need to be cleaned
>>> up as well...
>>>
>>> Let me know what you'd like me to try and tackle -- or if we need to bring these
>>> items up at the TSC for recommendation.
>>
>> I'm proposing this change so far:
>>
>> http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/roorg&id=891ad22536b49d4fee066a5865ad730f791d36e9
>>
>> with those relocated files being removed from oe-core. Any objections to
>> that to start with?
>
> Why not put the recipes in meta-oe? I have need for e.g eds-dbus and would like to have that in meta-oe.
If it's acceptable within meta-oe (I don't see why this wouldn't be) it
certainly can be added there as well.. however, I was assuming the default was
meta-yocto and it not going into meta-oe until a separate merge step, process,
etc.. meta-oe would be made up of the existing OE components (not in core)
initially...
--Mark
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-03-02 18:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 17:30 oe-core cleanup Mark Hatle
2011-03-02 18:00 ` Richard Purdie
2011-03-02 18:27 ` Koen Kooi
2011-03-02 18:33 ` Mark Hatle [this message]
2011-03-02 19:18 ` Richard Purdie
2011-03-03 0:58 ` Tom Rini
2011-03-03 8:02 ` Koen Kooi
2011-03-03 12:10 ` Richard Purdie
2011-03-03 14:43 ` Mark Hatle
2011-03-03 14:49 ` Tom Rini
2011-03-03 12:46 ` Koen Kooi
2011-03-03 13:09 ` Joshua Lock
2011-03-03 13:57 ` Koen Kooi
2011-03-03 14:05 ` Joshua Lock
2011-03-03 14:14 ` Chris Larson
2011-03-03 14:21 ` Chris Larson
2011-03-03 14:31 ` Joshua Lock
2011-03-03 14:29 ` Joshua Lock
2011-03-03 14:15 ` Chris Larson
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=4D6E8D8B.7030906@windriver.com \
--to=mark.hatle@windriver.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.