From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.windriver.com ([147.11.1.11]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1PupvO-0003Zk-Gm for openembedded-core@lists.openembedded.org; Wed, 02 Mar 2011 18:33:22 +0100 Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail.windriver.com (8.14.3/8.14.3) with ESMTP id p22HVqgX018987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Wed, 2 Mar 2011 09:31:52 -0800 (PST) Received: from Macintosh-5.local (172.25.36.227) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.1.255.0; Wed, 2 Mar 2011 09:31:52 -0800 Message-ID: <4D6E7EB1.5080602@windriver.com> Date: Wed, 2 Mar 2011 11:30:25 -0600 From: Mark Hatle Organization: Wind River Systems User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.14) Gecko/20110221 Thunderbird/3.1.8 MIME-Version: 1.0 To: Patches and discussions about the oe-core layer X-Originating-IP: [172.25.36.227] Subject: oe-core cleanup... X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2011 17:33:22 -0000 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit 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. --Mark