From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bear.ext.ti.com (bear.ext.ti.com [192.94.94.41]) by arago-project.org (Postfix) with ESMTPS id 798B652A10 for ; Thu, 11 Oct 2012 03:12:35 +0000 (UTC) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id q9B3CYMT023471 for ; Wed, 10 Oct 2012 22:12:34 -0500 Received: from DFLE72.ent.ti.com (dfle72.ent.ti.com [128.247.5.109]) by dlelxv30.itg.ti.com (8.13.8/8.13.8) with ESMTP id q9B3CYZY005838 for ; Wed, 10 Oct 2012 22:12:34 -0500 Received: from dlelxv22.itg.ti.com (172.17.1.197) by dfle72.ent.ti.com (128.247.5.109) with Microsoft SMTP Server id 14.1.323.3; Wed, 10 Oct 2012 22:12:34 -0500 Received: from localhost ([158.218.102.158]) by dlelxv22.itg.ti.com (8.13.8/8.13.8) with ESMTP id q9B3CXaC027353; Wed, 10 Oct 2012 22:12:34 -0500 Date: Wed, 10 Oct 2012 23:12:32 -0400 From: Denys Dmytriyenko To: "Cooper Jr., Franklin" Message-ID: <20121011031231.GD17839@edge> References: <20121010185225.GC32682@edge> <20121010185513.GD16944@denix.org> <9EA37CA2-92CB-4988-9E82-9D39A13B0F3C@ti.com> <7D46E86EC0A8354091174257B2FED10159257395@DLEE12.ent.ti.com> <20121010195738.GF16944@denix.org> <7D46E86EC0A8354091174257B2FED10159257515@DLEE12.ent.ti.com> <20121011025110.GB17839@edge> <9769EB7C-4976-4506-8936-C3CCB7687A1C@ti.com> <20121011025538.GC17839@edge> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "meta-arago@arago-project.org" Subject: Re: [meta-arago-extras][PATCH] ti-tisdk-setup: Port ti-tisdk-setup from arago X-BeenThere: meta-arago@arago-project.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Arago metadata layer for TI SDKs - OE-Core/Yocto compatible List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2012 03:12:35 -0000 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline On Wed, Oct 10, 2012 at 11:00:28PM -0400, Cooper Jr., Franklin wrote: > Most likely TI-tisdk-license will have a similar problem as this recipe. Can > we go ahead and create a repo for that one also? Its the recipe that > packages all the different licenses for the sdk software manifest. I plan to > submit it tomorrow. Can we reuse oe-core/meta/files/common-licenses/? > On Oct 10, 2012, at 9:55 PM, "Dmytriyenko, Denys" wrote: > > > On Wed, Oct 10, 2012 at 10:53:27PM -0400, Cooper Jr., Franklin wrote: > >> Me > > > > Ok, you too. > > > >> On Oct 10, 2012, at 9:51 PM, "Dmytriyenko, Denys" wrote: > >> > >>> On Wed, Oct 10, 2012 at 04:01:17PM -0400, Maupin, Chase wrote: > >>>>> -----Original Message----- > >>>>> From: Dmytriyenko, Denys > >>>>> Sent: Wednesday, October 10, 2012 2:58 PM > >>>>> To: Maupin, Chase > >>>>> Cc: Cooper Jr., Franklin; Dmytriyenko, Denys; meta-arago@arago- > >>>>> project.org > >>>>> Subject: Re: [meta-arago] [meta-arago-extras][PATCH] ti-tisdk- > >>>>> setup: Port ti-tisdk-setup from arago > >>>>> > >>>>> On Wed, Oct 10, 2012 at 07:43:08PM +0000, Maupin, Chase wrote: > >>>>>> There are lots of tweaks to the actual scripts that would be > >>>>> nice, but aside > >>>>>> from that no. They all need to go into an SDK. They make up a > >>>>> large part > >>>>>> of the OOBE and they tend to go together. The only one that > >>>>> could be > >>>>>> separated (in that it is not a dependecy for another one) would > >>>>> be > >>>>>> create-sdcard.sh but we consider that script as critical as all > >>>>> the others > >>>>>> and a mandatory install as part of the setup for an SDK. > >>>>> > >>>>> First of all, let's cut the patch from the email - I'm tired > >>>>> going to the > >>>>> administrative interface to approve the oversize message to the > >>>>> list... :) > >>>>> > >>>>> Second, why can't we have a separate git repository for all those > >>>>> shell > >>>>> scripts that are used for OOBE - you'll get version control and > >>>>> move the bulk > >>>>> outside of the metadata. Is it feasible? > >>>> > >>>> I'm OK with a separate git repo. Can you create a tisdk-setup-scripts repo > >>>> on arago for us? > >>> > >>> You know I can, and I did :) Who do you want in contributors, besides > >>> yourself? > >>> > >>> -- > >>> Denys