From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from comal.ext.ti.com (comal.ext.ti.com [198.47.26.152]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 02E94E00533 for ; Sat, 1 Sep 2012 14:07:32 -0700 (PDT) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by comal.ext.ti.com (8.13.7/8.13.7) with ESMTP id q81L7WIn015281 for ; Sat, 1 Sep 2012 16:07:32 -0500 Received: from DLEE74.ent.ti.com (dlee74.ent.ti.com [157.170.170.8]) by dlelxv30.itg.ti.com (8.13.8/8.13.8) with ESMTP id q81L7Wd2011113 for ; Sat, 1 Sep 2012 16:07:32 -0500 Received: from DFLE09.ent.ti.com ([fe80::3103:58c3:47f:860b]) by DLEE74.ent.ti.com ([fe80::a0f1:125b:e7e3:7ed8%18]) with mapi id 14.01.0323.003; Sat, 1 Sep 2012 16:07:32 -0500 From: "Cooper Jr., Franklin" To: "meta-ti@yoctoproject.org" Thread-Topic: Fix image recipes in meta-ti Thread-Index: Ac2Ig7pGwFxbqvJjRsORVyoWs1t29w== Date: Sat, 1 Sep 2012 21:07:31 +0000 Message-ID: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [157.170.170.90] MIME-Version: 1.0 Subject: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2012 21:07:33 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_8F29D6B095ED194EA1980491A5E029710C2B2B46DFLE09entticom_" --_000_8F29D6B095ED194EA1980491A5E029710C2B2B46DFLE09entticom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable When debugging issues in meta-arago I frequently try building recipes using= the meta-ti,meta-oe and oe-core layers. However, I always have to remove = the following recipes due to "This recipe does not have the LICENSE field s= et" error: cloud9-gfx-image.bb cloud9-gnome-image.bb cloud9-image.bb The issue is these recipes have an include from meta-angstrom that provides= this LICENSE field. Meta-ti should not have this dependency so these recip= es should be fixed to address this. I personally do not think cloud9 relate= d recipes that install cloud9, nodejs, mplayer etc.. should even be in met= a-ti which is a BSP layer but that is a completely different discussion. I = also don't believe pulling in the include file that is needed from meta-ang= strom is also a reasonably solution. Either these recipes need to be fixed = so that they can work in meta-ti with only a dependency on meta-oe and oe-c= ore. Or remove the recipes from this layer and pull it into meta-angstrom w= hich I believe is the best option. Regards, Franklin Cooper Jr. Texas Instruments Application Engineer fcooper@ti.com --_000_8F29D6B095ED194EA1980491A5E029710C2B2B46DFLE09entticom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

When debugging issues in meta-arago I frequently try= building recipes using  the meta-ti,meta-oe and oe-core layers. Howev= er, I always have to remove the following recipes due to “This recipe= does not have the LICENSE field set” error:

cloud9-gfx-image.bb

cloud9-gnome-image.bb

cloud9-image.bb

 

The issue is these recipes have an include from meta= -angstrom that provides this LICENSE field. Meta-ti should not have this de= pendency so these recipes should be fixed to address this. I personally do = not think cloud9 related recipes that install  cloud9, nodejs, mplayer etc.. should even be in meta-ti whic= h is a BSP layer but that is a completely different discussion. I also don&= #8217;t believe pulling in the include file that is needed from meta-angstr= om is also a reasonably solution. Either these recipes need to be fixed so that they can work in meta-ti with only a depe= ndency on meta-oe and oe-core. Or remove the recipes from this layer and pu= ll it into meta-angstrom which I believe is the best option.

Regards,

Franklin Cooper Jr.

Texas Instruments

Application Engineer

fcooper@ti.com=

 

--_000_8F29D6B095ED194EA1980491A5E029710C2B2B46DFLE09entticom_-- 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 yocto-www.yoctoproject.org (Postfix) with ESMTP id 8F79EE00533 for ; Sat, 1 Sep 2012 14:14:44 -0700 (PDT) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id q81LEiIn006559 for ; Sat, 1 Sep 2012 16:14:44 -0500 Received: from DLEE74.ent.ti.com (dlee74.ent.ti.com [157.170.170.8]) by dlelxv30.itg.ti.com (8.13.8/8.13.8) with ESMTP id q81LEig1016738 for ; Sat, 1 Sep 2012 16:14:44 -0500 Received: from DFLE12.ent.ti.com ([fe80::145d:e72a:4dbf:e0dd]) by DLEE74.ent.ti.com ([fe80::a0f1:125b:e7e3:7ed8%18]) with mapi id 14.01.0323.003; Sat, 1 Sep 2012 16:14:43 -0500 From: "Kridner, Jason" To: "Cooper Jr., Franklin" , "meta-ti@yoctoproject.org" Thread-Topic: [meta-ti] Fix image recipes in meta-ti Thread-Index: AQHNiIbO21yNTP9P5kWsNbGiZYGBzA== Date: Sat, 1 Sep 2012 21:14:43 +0000 Message-ID: References: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 Subject: Re: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2012 21:14:44 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_kkitbg3uuuda8t5puice0pub1346534080222emailandroidcom_" --_000_kkitbg3uuuda8t5puice0pub1346534080222emailandroidcom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Will meta-oe take the recipes? -------- Original message -------- Subject: [meta-ti] Fix image recipes in meta-ti From: "Cooper Jr., Franklin" To: "meta-ti@yoctoproject.org" CC: When debugging issues in meta-arago I frequently try building recipes using= the meta-ti,meta-oe and oe-core layers. However, I always have to remove = the following recipes due to =93This recipe does not have the LICENSE field= set=94 error: cloud9-gfx-image.bb cloud9-gnome-image.bb cloud9-image.bb The issue is these recipes have an include from meta-angstrom that provides= this LICENSE field. Meta-ti should not have this dependency so these recip= es should be fixed to address this. I personally do not think cloud9 relate= d recipes that install cloud9, nodejs, mplayer etc.. should even be in met= a-ti which is a BSP layer but that is a completely different discussion. I = also don=92t believe pulling in the include file that is needed from meta-a= ngstrom is also a reasonably solution. Either these recipes need to be fixe= d so that they can work in meta-ti with only a dependency on meta-oe and oe= -core. Or remove the recipes from this layer and pull it into meta-angstrom= which I believe is the best option. Regards, Franklin Cooper Jr. Texas Instruments Application Engineer fcooper@ti.com --_000_kkitbg3uuuda8t5puice0pub1346534080222emailandroidcom_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Will meta-oe take the recipes? 


-------- Original message --------
Subject: [meta-ti] Fix image recipes in meta-ti
From: "Cooper Jr., Franklin" <fcooper@ti.com>
To: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org> <= br> CC:


When debugging issues in meta-arago I frequently try= building recipes using  the meta-ti,meta-oe and oe-core layers. Howev= er, I always have to remove the following recipes due to =93This recipe doe= s not have the LICENSE field set=94 error:

cloud9-gfx-image.bb

cloud9-gnome-image.bb

cloud9-image.bb

 

The issue is these recipes have an include from meta= -angstrom that provides this LICENSE field. Meta-ti should not have this de= pendency so these recipes should be fixed to address this. I personally do = not think cloud9 related recipes that install  cloud9, nodejs, mplayer etc.. should even be in meta-ti whic= h is a BSP layer but that is a completely different discussion. I also don= =92t believe pulling in the include file that is needed from meta-angstrom = is also a reasonably solution. Either these recipes need to be fixed so that they can work in meta-ti with only a depe= ndency on meta-oe and oe-core. Or remove the recipes from this layer and pu= ll it into meta-angstrom which I believe is the best option.

Regards,

Franklin Cooper Jr.

Texas Instruments

Application Engineer

fcooper@ti.com=

 

--_000_kkitbg3uuuda8t5puice0pub1346534080222emailandroidcom_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from devils.ext.ti.com (devils.ext.ti.com [198.47.26.153]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3DA56E00533 for ; Sat, 1 Sep 2012 14:21:13 -0700 (PDT) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by devils.ext.ti.com (8.13.7/8.13.7) with ESMTP id q81LLCU5014058 for ; Sat, 1 Sep 2012 16:21:12 -0500 Received: from DFLE73.ent.ti.com (dfle73.ent.ti.com [128.247.5.110]) by dlelxv30.itg.ti.com (8.13.8/8.13.8) with ESMTP id q81LLCk5022984 for ; Sat, 1 Sep 2012 16:21:12 -0500 Received: from DFLE09.ent.ti.com ([fe80::3103:58c3:47f:860b]) by DFLE73.ent.ti.com ([fe80::86e:fab6:cd95:e158%28]) with mapi id 14.01.0323.003; Sat, 1 Sep 2012 16:21:12 -0500 From: "Cooper Jr., Franklin" To: "Kridner, Jason" Thread-Topic: [meta-ti] Fix image recipes in meta-ti Thread-Index: Ac2Ig7pGwFxbqvJjRsORVyoWs1t29wALPzCA//+t/rs= Date: Sat, 1 Sep 2012 21:21:12 +0000 Message-ID: References: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com>, In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 Cc: "meta-ti@yoctoproject.org" Subject: Re: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2012 21:21:13 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B3DA41A93C2F4C4EA41468BA6D249EF7ticom_" --_000_B3DA41A93C2F4C4EA41468BA6D249EF7ticom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Unless the meta-angstrom dependency is fixed then I would see them having t= he same issue. On Sep 1, 2012, at 4:14 PM, "Kridner, Jason" = > wrote: Will meta-oe take the recipes? -------- Original message -------- Subject: [meta-ti] Fix image recipes in meta-ti From: "Cooper Jr., Franklin" > To: "meta-ti@yoctoproject.org" > CC: When debugging issues in meta-arago I frequently try building recipes using= the meta-ti,meta-oe and oe-core layers. However, I always have to remove = the following recipes due to =93This recipe does not have the LICENSE field= set=94 error: cloud9-gfx-image.bb cloud9-gnome-image.bb cloud9-image.bb The issue is these recipes have an include from meta-angstrom that provides= this LICENSE field. Meta-ti should not have this dependency so these recip= es should be fixed to address this. I personally do not think cloud9 relate= d recipes that install cloud9, nodejs, mplayer etc.. should even be in met= a-ti which is a BSP layer but that is a completely different discussion. I = also don=92t believe pulling in the include file that is needed from meta-a= ngstrom is also a reasonably solution. Either these recipes need to be fixe= d so that they can work in meta-ti with only a dependency on meta-oe and oe= -core. Or remove the recipes from this layer and pull it into meta-angstrom= which I believe is the best option. Regards, Franklin Cooper Jr. Texas Instruments Application Engineer fcooper@ti.com --_000_B3DA41A93C2F4C4EA41468BA6D249EF7ticom_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Unless the meta-angstrom dependency is fixed then I would see them hav= ing the same issue.

On Sep 1, 2012, at 4:14 PM, "Kridner, Jason" <jdk@ti.com> wrote:

Will meta-oe take the recipes? 


-------- Original message --------
Subject: [meta-ti] Fix image recipes in meta-ti
From: "Cooper Jr., Franklin" <fcooper@ti.com>
To: "meta-ti@yoctoproject.= org" <meta-ti@yocto= project.org>
CC:


When debugging issues in meta-arago I frequently try= building recipes using  the meta-ti,meta-oe and oe-core layers. Howev= er, I always have to remove the following recipes due to =93This recipe doe= s not have the LICENSE field set=94 error:

cloud9-gfx-image.bb

cloud9-gnome-image.bb

cloud9-image.bb

 

The issue is these recipes have an include from meta= -angstrom that provides this LICENSE field. Meta-ti should not have this de= pendency so these recipes should be fixed to address this. I personally do = not think cloud9 related recipes that install  cloud9, nodejs, mplayer etc.. should even be in meta-ti whic= h is a BSP layer but that is a completely different discussion. I also don= =92t believe pulling in the include file that is needed from meta-angstrom = is also a reasonably solution. Either these recipes need to be fixed so that they can work in meta-ti with only a depe= ndency on meta-oe and oe-core. Or remove the recipes from this layer and pu= ll it into meta-angstrom which I believe is the best option.

Regards,

Franklin Cooper Jr.

Texas Instruments

Application Engineer

fcooper@ti.com=

 

--_000_B3DA41A93C2F4C4EA41468BA6D249EF7ticom_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from devils.ext.ti.com (devils.ext.ti.com [198.47.26.153]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 70D30E00533 for ; Sat, 1 Sep 2012 14:33:25 -0700 (PDT) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by devils.ext.ti.com (8.13.7/8.13.7) with ESMTP id q81LXOk0014538 for ; Sat, 1 Sep 2012 16:33:24 -0500 Received: from DFLE73.ent.ti.com (dfle73.ent.ti.com [128.247.5.110]) by dlelxv30.itg.ti.com (8.13.8/8.13.8) with ESMTP id q81LXOri000776 for ; Sat, 1 Sep 2012 16:33:24 -0500 Received: from DLEE12.ent.ti.com ([fe80::3867:617:aab3:5956]) by DFLE73.ent.ti.com ([fe80::86e:fab6:cd95:e158%28]) with mapi id 14.01.0323.003; Sat, 1 Sep 2012 16:33:24 -0500 From: "Maupin, Chase" To: "Cooper Jr., Franklin" , "meta-ti@yoctoproject.org" Thread-Topic: [meta-ti] Fix image recipes in meta-ti Thread-Index: AQHNiIlqwFKpIXcwBU2JhvnT55RIdQ== Date: Sat, 1 Sep 2012 21:33:24 +0000 Message-ID: <07A98304-6F3A-424E-820E-FCAC8B3C0039@ti.com> References: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 Subject: Re: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2012 21:33:25 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_07A983046F3A424E820EFCAC8B3C0039ticom_" --_000_07A983046F3A424E820EFCAC8B3C0039ticom_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Agreed for my two cents. Sent from my cell phone ----- Reply message ----- From: "Cooper Jr., Franklin" Date: Sat, Sep 1, 2012 4:07 pm Subject: [meta-ti] Fix image recipes in meta-ti To: "meta-ti@yoctoproject.org" When debugging issues in meta-arago I frequently try building recipes using= the meta-ti,meta-oe and oe-core layers. However, I always have to remove = the following recipes due to =93This recipe does not have the LICENSE field= set=94 error: cloud9-gfx-image.bb cloud9-gnome-image.bb cloud9-image.bb The issue is these recipes have an include from meta-angstrom that provides= this LICENSE field. Meta-ti should not have this dependency so these recip= es should be fixed to address this. I personally do not think cloud9 relate= d recipes that install cloud9, nodejs, mplayer etc.. should even be in met= a-ti which is a BSP layer but that is a completely different discussion. I = also don=92t believe pulling in the include file that is needed from meta-a= ngstrom is also a reasonably solution. Either these recipes need to be fixe= d so that they can work in meta-ti with only a dependency on meta-oe and oe= -core. Or remove the recipes from this layer and pull it into meta-angstrom= which I believe is the best option. Regards, Franklin Cooper Jr. Texas Instruments Application Engineer fcooper@ti.com --_000_07A983046F3A424E820EFCAC8B3C0039ticom_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Agreed for my two cents.

Sent from my cell phone

----- Reply message -----
From: "Cooper Jr., Franklin" <fcooper@ti.com>
Date: Sat, Sep 1, 2012 4:07 pm
Subject: [meta-ti] Fix image recipes in meta-ti
To: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>

When debugging issues in meta-arago I frequently try= building recipes using  the meta-ti,meta-oe and oe-core layers. Howev= er, I always have to remove the following recipes due to =93This recipe doe= s not have the LICENSE field set=94 error:

cloud9-gfx-image.bb

cloud9-gnome-image.bb

cloud9-image.bb

 

The issue is these recipes have an include from meta= -angstrom that provides this LICENSE field. Meta-ti should not have this de= pendency so these recipes should be fixed to address this. I personally do = not think cloud9 related recipes that install  cloud9, nodejs, mplayer etc.. should even be in meta-ti whic= h is a BSP layer but that is a completely different discussion. I also don= =92t believe pulling in the include file that is needed from meta-angstrom = is also a reasonably solution. Either these recipes need to be fixed so that they can work in meta-ti with only a depe= ndency on meta-oe and oe-core. Or remove the recipes from this layer and pu= ll it into meta-angstrom which I believe is the best option.

Regards,

Franklin Cooper Jr.

Texas Instruments

Application Engineer

fcooper@ti.com=

 

--_000_07A983046F3A424E820EFCAC8B3C0039ticom_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from vms173019pub.verizon.net (vms173019pub.verizon.net [206.46.173.19]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id E2A4EE00533 for ; Sat, 1 Sep 2012 15:48:24 -0700 (PDT) Received: from gandalf.denix.org ([unknown] [72.66.25.115]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0M9P007720NQVX60@vms173019.mailsrvcs.net> for meta-ti@yoctoproject.org; Sat, 01 Sep 2012 17:48:06 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id B092F201AF; Sat, 01 Sep 2012 18:47:50 -0400 (EDT) Date: Sat, 01 Sep 2012 18:47:50 -0400 From: Denys Dmytriyenko To: "Cooper Jr., Franklin" Message-id: <20120901224750.GD11821@denix.org> References: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> MIME-version: 1.0 In-reply-to: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "meta-ti@yoctoproject.org" Subject: Re: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2012 22:48:25 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Sat, Sep 01, 2012 at 09:07:31PM +0000, Cooper Jr., Franklin wrote: > When debugging issues in meta-arago I frequently try building recipes using > the meta-ti,meta-oe and oe-core layers. However, I always have to remove the > following recipes due to "This recipe does not have the LICENSE field set" > error: > cloud9-gfx-image.bb > cloud9-gnome-image.bb > cloud9-image.bb FWIW, meta-arago explicitly masks those recipes, so you shouldn't be having those errors or have to remove the recipes: http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-distro/conf/distro/arago.conf;hb=HEAD#l2 Also, it was discussed here just few days ago: https://lists.yoctoproject.org/pipermail/meta-ti/2012-August/001456.html > The issue is these recipes have an include from meta-angstrom that provides > this LICENSE field. Meta-ti should not have this dependency so these recipes > should be fixed to address this. I personally do not think cloud9 related > recipes that install cloud9, nodejs, mplayer etc.. should even be in > meta-ti which is a BSP layer but that is a completely different discussion. > I also don't believe pulling in the include file that is needed from > meta-angstrom is also a reasonably solution. Either these recipes need to be > fixed so that they can work in meta-ti with only a dependency on meta-oe and > oe-core. Or remove the recipes from this layer and pull it into > meta-angstrom which I believe is the best option. So, what do you propose? ;) Or you just volunteering to be in the middle of a flame war by raising this hard issue? -- Denys 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 yocto-www.yoctoproject.org (Postfix) with ESMTP id 70077E00533 for ; Sat, 1 Sep 2012 15:56:19 -0700 (PDT) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id q81MuIQq011191 for ; Sat, 1 Sep 2012 17:56:18 -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 q81MuIis024696 for ; Sat, 1 Sep 2012 17:56:18 -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; Sat, 1 Sep 2012 17:56:18 -0500 Received: from localhost ([158.218.102.158]) by dlelxv22.itg.ti.com (8.13.8/8.13.8) with ESMTP id q81MuIQS001840; Sat, 1 Sep 2012 17:56:18 -0500 Date: Sat, 1 Sep 2012 18:56:18 -0400 From: Denys Dmytriyenko To: "Kridner, Jason" Message-ID: <20120901225617.GF22219@edge> References: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "meta-ti@yoctoproject.org" Subject: Re: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2012 22:56:19 -0000 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline On Sat, Sep 01, 2012 at 09:14:43PM +0000, Kridner, Jason wrote: > Will meta-oe take the recipes? Well, those maybe better suited for meta-angstrom instead... If you think about it - cloud9 is an important component of default Beaglebone images based on Angstrom, so images with the cloud9 in the name are naturally associated with Angstrom. Anybody else who'd like to use meta-ti as BSP layer outside of Angstrom would most probably use own images anyway... -- Denys > -------- Original message -------- > Subject: [meta-ti] Fix image recipes in meta-ti > From: "Cooper Jr., Franklin" > To: "meta-ti@yoctoproject.org" > CC: > > > When debugging issues in meta-arago I frequently try building recipes using > the meta-ti,meta-oe and oe-core layers. However, I always have to remove the > following recipes due to ?This recipe does not have the LICENSE field set? > error: > cloud9-gfx-image.bb > cloud9-gnome-image.bb > cloud9-image.bb > > The issue is these recipes have an include from meta-angstrom that provides > this LICENSE field. Meta-ti should not have this dependency so these recipes > should be fixed to address this. I personally do not think cloud9 related > recipes that install cloud9, nodejs, mplayer etc.. should even be in > meta-ti which is a BSP layer but that is a completely different discussion. > I also don?t believe pulling in the include file that is needed from > meta-angstrom is also a reasonably solution. Either these recipes need to be > fixed so that they can work in meta-ti with only a dependency on meta-oe and > oe-core. Or remove the recipes from this layer and pull it into > meta-angstrom which I believe is the best option. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B8E8DE0049D for ; Sun, 2 Sep 2012 09:16:50 -0700 (PDT) Received: by wgx1 with SMTP id 1so2725248wgx.11 for ; Sun, 02 Sep 2012 09:16:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=4MsV7b6FhOYpZTAtJTMg0MtygeQtuynTH+BEek521Rs=; b=GNQZU6ccohddG28uQedRVWZGq7kK312YgalBYrsIFjU8/wujCodg6Ol4tksBd4Ip77 FChHC/HEh+0m6YeJPFvkp+/B+p010JkjN1UwDIih0GzhGpe28DZDmCG/dGx6Qp91sbr/ 8d/DbwnsNxL76C73Y6w3xDaAGoAEtukc5ztT9K0/rfM9Un9vD8DOU//6lY0DL0CaPXlZ WXWH/b8rUMmT0oMVXt5LcCCgjPbVtua1oUWoXcXjzb4Tgl+lSJQjsif8OAFV76ZCHphL E4rp+UDfV3Q//L7TrcU5JBAy0sGcG3x+HeEvP2FwaVS/QL5N+EJKr7MTY1bdoNRAs/k2 UMMQ== Received: by 10.180.74.133 with SMTP id t5mr17453474wiv.2.1346602609198; Sun, 02 Sep 2012 09:16:49 -0700 (PDT) Received: from [172.20.0.10] (ip4da2a5ae.direct-adsl.nl. [77.162.165.174]) by mx.google.com with ESMTPS id k2sm20558550wiz.7.2012.09.02.09.16.46 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 02 Sep 2012 09:16:47 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\)) From: Koen Kooi In-Reply-To: <20120901225617.GF22219@edge> Date: Sun, 2 Sep 2012 18:16:46 +0200 Message-Id: References: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> <20120901225617.GF22219@edge> To: Denys Dmytriyenko X-Mailer: Apple Mail (2.1486) X-Gm-Message-State: ALoCoQn5sB4NLk2u9HsvuWJsSMAyWxsaFItWlwNfCJzSToPmrFUiX/EZBwa6CoOl4Q4eAzzCM5HC Cc: "meta-ti@yoctoproject.org" Subject: Re: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Sep 2012 16:16:51 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Op 2 sep. 2012, om 00:56 heeft Denys Dmytriyenko het = volgende geschreven: > On Sat, Sep 01, 2012 at 09:14:43PM +0000, Kridner, Jason wrote: >> Will meta-oe take the recipes? >=20 > Well, those maybe better suited for meta-angstrom instead... If you = think=20 > about it - cloud9 is an important component of default Beaglebone = images based=20 > on Angstrom, so images with the cloud9 in the name are naturally = associated=20 > with Angstrom. Anybody else who'd like to use meta-ti as BSP layer = outside of=20 > Angstrom would most probably use own images anyway... I'd be happy to remove all those pesky beagleboard, beaglebone, = pandaboard, etc related recipes, machines, images from meta-ti if they = are causing such big, unsolvable problems for the TI SDK team.=20= From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from comal.ext.ti.com (comal.ext.ti.com [198.47.26.152]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B817CE0049D for ; Sun, 2 Sep 2012 11:07:34 -0700 (PDT) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by comal.ext.ti.com (8.13.7/8.13.7) with ESMTP id q82I7Xfh017081; Sun, 2 Sep 2012 13:07:33 -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 q82I7XrR025344; Sun, 2 Sep 2012 13:07:33 -0500 Received: from DFLE09.ent.ti.com ([fe80::3103:58c3:47f:860b]) by DFLE72.ent.ti.com ([fe80::5c48:b90d:af93:5822%30]) with mapi id 14.01.0323.003; Sun, 2 Sep 2012 13:07:33 -0500 From: "Cooper Jr., Franklin" To: Koen Kooi , "Dmytriyenko, Denys" Thread-Topic: [meta-ti] Fix image recipes in meta-ti Thread-Index: Ac2Ig7pGwFxbqvJjRsORVyoWs1t29wALPzCAAAOMOgAAJFZ/AAAH6Uxw Date: Sun, 2 Sep 2012 18:07:32 +0000 Message-ID: <8F29D6B095ED194EA1980491A5E029710C2B34AD@DFLE09.ent.ti.com> References: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> <20120901225617.GF22219@edge> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.247.5.50] MIME-Version: 1.0 Cc: "meta-ti@yoctoproject.org" Subject: Re: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Sep 2012 18:07:34 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I will reiterate my initial point. The argument if the mentioned recipes sh= ould even be in meta-ti is a completely different discussion and beyond the= scope of this discussion. The fact of the matter is meta-ti is broken unle= ss you depend on meta-angstrom which is wrong. As Denys' pointed out (https= ://lists.yoctoproject.org/pipermail/meta-ti/2012-August/001452.html) this i= s a "minor" issue but an issue that other people are experiencing. Koen you have brought up valid points before in other discussions about no= t placing things in meta-ti that can break things for other people. The sam= e logic applies here. All I want is a clean solution which will allow me to= use meta-ti in a distroless environment which I do frequently. How this is= accomplished I can care less. -----Original Message----- From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject= .org] On Behalf Of Koen Kooi Sent: Sunday, September 02, 2012 11:17 AM To: Dmytriyenko, Denys Cc: meta-ti@yoctoproject.org Subject: Re: [meta-ti] Fix image recipes in meta-ti Op 2 sep. 2012, om 00:56 heeft Denys Dmytriyenko het volgend= e geschreven: > On Sat, Sep 01, 2012 at 09:14:43PM +0000, Kridner, Jason wrote: >> Will meta-oe take the recipes? >=20 > Well, those maybe better suited for meta-angstrom instead... If you=20 > think about it - cloud9 is an important component of default=20 > Beaglebone images based on Angstrom, so images with the cloud9 in the=20 > name are naturally associated with Angstrom. Anybody else who'd like=20 > to use meta-ti as BSP layer outside of Angstrom would most probably use o= wn images anyway... I'd be happy to remove all those pesky beagleboard, beaglebone, pandaboard,= etc related recipes, machines, images from meta-ti if they are causing suc= h big, unsolvable problems for the TI SDK team.=20 _______________________________________________ meta-ti mailing list meta-ti@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-ti 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 yocto-www.yoctoproject.org (Postfix) with ESMTP id 6527EE0049D for ; Sun, 2 Sep 2012 12:47:18 -0700 (PDT) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id q82JlHbi012059; Sun, 2 Sep 2012 14:47:17 -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 q82JlHDq024056; Sun, 2 Sep 2012 14:47:17 -0500 Received: from DLEE12.ent.ti.com ([fe80::3867:617:aab3:5956]) by DFLE72.ent.ti.com ([fe80::5c48:b90d:af93:5822%30]) with mapi id 14.01.0323.003; Sun, 2 Sep 2012 14:47:17 -0500 From: "Maupin, Chase" To: "Cooper Jr., Franklin" Thread-Topic: [meta-ti] Fix image recipes in meta-ti Thread-Index: Ac2Ig7pGwFxbqvJjRsORVyoWs1t29wALPzCAAAOMOgAAJFZ/AAAH6Uxw//+ntWU= Date: Sun, 2 Sep 2012 19:47:16 +0000 Message-ID: <26A1186D-E714-4AD6-BB0E-1743FB6DFA2A@ti.com> References: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> <20120901225617.GF22219@edge> , <8F29D6B095ED194EA1980491A5E029710C2B34AD@DFLE09.ent.ti.com> In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C2B34AD@DFLE09.ent.ti.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 Cc: "meta-ti@yoctoproject.org" Subject: Re: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Sep 2012 19:47:18 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I agree with Denys and Franklin here. Meta-ti should be a straight BSP lay= er so we should remove distro dependencies. This is the same as moving net= base changes to meta-arago. There may be things in meta-ti that don't belo= ng there and they should be moved to the appropriate location I understand that you have been using meta-ti and leading the way here, bu= t that does not mean that we can't work together in this layer going forwar= d. You may have noticed that most of the TI SDK stuff has been going into = meta-arago since that is where it belongs. We are trying hard not to put t= hings in meta-ti that will force others to use the arago distribution, I wo= uldask that we make sure the same applies for Angstrom as well, or any othe= r distribution for that matter. I'm confused where the objection is to moving these recipes that rely on t= he Angstrom layer into the actual Angstrom layer? Let's discuss that topic= and how we can structure this layer to meet everyone's needs. That would = likely be more productive and save us all frustration. Sincerely, Chase Maupin On Sep 2, 2012, at 1:07 PM, "Cooper Jr., Franklin" wrote: > I will reiterate my initial point. The argument if the mentioned recipes= should even be in meta-ti is a completely different discussion and beyond = the scope of this discussion. The fact of the matter is meta-ti is broken u= nless you depend on meta-angstrom which is wrong. As Denys' pointed out (ht= tps://lists.yoctoproject.org/pipermail/meta-ti/2012-August/001452.html) thi= s is a "minor" issue but an issue that other people are experiencing. >=20 > Koen you have brought up valid points before in other discussions about = not placing things in meta-ti that can break things for other people. The s= ame logic applies here. All I want is a clean solution which will allow me = to use meta-ti in a distroless environment which I do frequently. How this = is accomplished I can care less. >=20 > -----Original Message----- > From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproj= ect.org] On Behalf Of Koen Kooi > Sent: Sunday, September 02, 2012 11:17 AM > To: Dmytriyenko, Denys > Cc: meta-ti@yoctoproject.org > Subject: Re: [meta-ti] Fix image recipes in meta-ti >=20 >=20 > Op 2 sep. 2012, om 00:56 heeft Denys Dmytriyenko het volg= ende geschreven: >=20 >> On Sat, Sep 01, 2012 at 09:14:43PM +0000, Kridner, Jason wrote: >>> Will meta-oe take the recipes? >>=20 >> Well, those maybe better suited for meta-angstrom instead... If you=20 >> think about it - cloud9 is an important component of default=20 >> Beaglebone images based on Angstrom, so images with the cloud9 in the= =20 >> name are naturally associated with Angstrom. Anybody else who'd like=20 >> to use meta-ti as BSP layer outside of Angstrom would most probably use= own images anyway... >=20 > I'd be happy to remove all those pesky beagleboard, beaglebone, pandaboa= rd, etc related recipes, machines, images from meta-ti if they are causing = such big, unsolvable problems for the TI SDK team.=20 > _______________________________________________ > meta-ti mailing list > meta-ti@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-ti > _______________________________________________ > meta-ti mailing list > meta-ti@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-ti From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ey0-f176.google.com (mail-ey0-f176.google.com [209.85.215.176]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9C078E0049D for ; Sun, 2 Sep 2012 14:11:20 -0700 (PDT) Received: by eabd1 with SMTP id d1so1521511eab.35 for ; Sun, 02 Sep 2012 14:11:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=miJGYTto0uuTYebT1/NHQjzBPseLKbI6EfijnJse84c=; b=YAD+gmPLKRLUKBKUT38IukKdiIMR8Yaj59082X8edWEL2L6KSxVJdl92QKX3Y3H0ro fAhUnXjXrQoLVX1pxc0/VXUVeTGl3QPDUk1X6xtLEIlUVatN7r69zIPkp3qSTbS0KCWB DtdL1iGznUGRehWN/XKh5Iyi88U2t62whBo+lh6ELH2H/V57dwivy4c6N8XqKgg5qAu8 DcauPjC9E2fZLhCB1Pv1Sfpzq4c7/Dh6DrHbjwsgAFkVurjCmHND8WQptuPjaP0G8puV yILsZwcdNNC7/yOeYCDFRBoivO5tYXt2yehs5PCtMDrbcuY9XVlpU2ZSGOnW3CiElhtI I+Pg== Received: by 10.14.215.193 with SMTP id e41mr18793449eep.44.1346620276682; Sun, 02 Sep 2012 14:11:16 -0700 (PDT) Received: from ?IPv6:2001:610:612::91cb:5d29:e17:5fb? ([2001:610:612:0:91cb:5d29:e17:5fb]) by mx.google.com with ESMTPS id 45sm30905905eeb.8.2012.09.02.14.11.14 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 02 Sep 2012 14:11:15 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\)) From: Koen Kooi In-Reply-To: <26A1186D-E714-4AD6-BB0E-1743FB6DFA2A@ti.com> Date: Sun, 2 Sep 2012 23:11:13 +0200 Message-Id: <2A0DAC13-04B3-4E44-B278-B6A22233C86D@dominion.thruhere.net> References: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> <20120901225617.GF22219@edge> , <8F29D6B095ED194EA1980491A5E029710C2B34AD@DFLE09.ent.ti.com> <26A1186D-E714-4AD6-BB0E-1743FB6DFA2A@ti.com> To: "meta-ti@yoctoproject.org" X-Mailer: Apple Mail (2.1486) X-Gm-Message-State: ALoCoQm6Cm+Q/Eat05m1P16w5KRSvggvo4yf1ple36O9YYaSrK5zwICJXnGylBqw0A/KISyajYLs Subject: Re: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Sep 2012 21:11:21 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Op 2 sep. 2012, om 21:47 heeft "Maupin, Chase" het = volgende geschreven: > I agree with Denys and Franklin here. Meta-ti should be a straight = BSP layer so we should remove distro dependencies. This is the same as = moving netbase changes to meta-arago. I'm not sure if what you mean by this example. The current netbase patch = is the second try to get it into meta-ti, will there be a 3rd try?=20 > There may be things in meta-ti that don't belong there and they = should be moved to the appropriate location And I completely agree. > I understand that you have been using meta-ti and leading the way = here, but that does not mean that we can't work together in this layer = going forward. You may have noticed that most of the TI SDK stuff has = been going into meta-arago since that is where it belongs. We are = trying hard not to put things in meta-ti that will force others to use = the arago distribution, I wouldask that we make sure the same applies = for Angstrom as well, or any other distribution for that matter. So show me where it is being forced. Really. There are no requires, only = includes. So if you mean by 'forcing' that a few warnings may scroll by = than, yes, it's being 'forced'. If you mean that the only way to use = meta-ti is by using angstrom, than no, it's not being 'forced'. So = instead of spreading more FUD, can you please use more precise language = for the problem at hand? As I said above, I agree that those images = don't belong in meta-ti. But funnily enough, that was not my decision. I = was told to keep them there. By TI. > I'm confused where the objection is to moving these recipes that rely = on the Angstrom layer into the actual Angstrom layer? For one, it was TI that objected to it. I don't care if some part of TI = is now changing course on that. I care if some other part of TI is going = to change course again in a few weeks. Just make a clear decision and = stick with it instead of not doing a thing and rekindling the same old = discussion every other month. For two: They don't belong in the angstrom layer either, they are way = too machine/SoC specific for that. > Let's discuss that topic and how we can structure this layer to meet = everyone's needs. That would likely be more productive and save us all = frustration. Like I said, I have no problem at all removing all beagle, bone and = panda related things from meta-ti. In a previous incarnation of this = discussion I offered to do that and was told by TI to keep everything = in, both by SDO and AMBU people. So I'll offer it again now. So if you = don't like that proposal, make a counter proposal. Being an external contributor for the past 6 months has given me a good = sense of what works and what doesn't work and what the level of = (non)support the community can expect from TI. To be clear: Denys is = doing an awesome job managing meta-ti, someone send him some cookies. You work for TI, you get to dictate what happens in meta-ti, so make a = proposal. I'm only a small part of the community, I have no illusions of = being able to influence the direction of meta-ti. I can however look at = your proposal and give my opinion on it.= From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from comal.ext.ti.com (comal.ext.ti.com [198.47.26.152]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 417E5E00344 for ; Tue, 4 Sep 2012 06:53:44 -0700 (PDT) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by comal.ext.ti.com (8.13.7/8.13.7) with ESMTP id q84DrgeX025665; Tue, 4 Sep 2012 08:53:42 -0500 Received: from DLEE74.ent.ti.com (dlee74.ent.ti.com [157.170.170.8]) by dlelxv30.itg.ti.com (8.13.8/8.13.8) with ESMTP id q84DrgDg006015; Tue, 4 Sep 2012 08:53:42 -0500 Received: from DLEE12.ent.ti.com ([fe80::3867:617:aab3:5956]) by DLEE74.ent.ti.com ([fe80::a0f1:125b:e7e3:7ed8%18]) with mapi id 14.01.0323.003; Tue, 4 Sep 2012 08:53:42 -0500 From: "Maupin, Chase" To: Koen Kooi , "meta-ti@yoctoproject.org" Thread-Topic: [meta-ti] Fix image recipes in meta-ti Thread-Index: Ac2Ig7pGwFxbqvJjRsORVyoWs1t29wALPzCAAAOMOgAAJFZ/AAAH6Uxw//+ntWWAAGtFgP/9qo7g Date: Tue, 4 Sep 2012 13:53:42 +0000 Message-ID: <7D46E86EC0A8354091174257B2FED101591C76F0@DLEE12.ent.ti.com> References: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> <20120901225617.GF22219@edge> , <8F29D6B095ED194EA1980491A5E029710C2B34AD@DFLE09.ent.ti.com> <26A1186D-E714-4AD6-BB0E-1743FB6DFA2A@ti.com> <2A0DAC13-04B3-4E44-B278-B6A22233C86D@dominion.thruhere.net> In-Reply-To: <2A0DAC13-04B3-4E44-B278-B6A22233C86D@dominion.thruhere.net> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.247.5.50] MIME-Version: 1.0 Subject: Re: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Sep 2012 13:53:44 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable > -----Original Message----- > From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti- > bounces@yoctoproject.org] On Behalf Of Koen Kooi > Sent: Sunday, September 02, 2012 4:11 PM > To: meta-ti@yoctoproject.org > Subject: Re: [meta-ti] Fix image recipes in meta-ti >=20 >=20 > Op 2 sep. 2012, om 21:47 heeft "Maupin, Chase" > het volgende geschreven: >=20 > > I agree with Denys and Franklin here. Meta-ti should be a > straight BSP layer so we should remove distro dependencies. This > is the same as moving netbase changes to meta-arago. >=20 > I'm not sure if what you mean by this example. The current > netbase patch is the second try to get it into meta-ti, will > there be a 3rd try? This will be moved to meta-arago based on your feedback. I think there wer= e some questions about what you meant but it is understood now. >=20 > > There may be things in meta-ti that don't belong there and > they should be moved to the appropriate location >=20 > And I completely agree. >=20 > > I understand that you have been using meta-ti and leading the > way here, but that does not mean that we can't work together in > this layer going forward. You may have noticed that most of the > TI SDK stuff has been going into meta-arago since that is where > it belongs. We are trying hard not to put things in meta-ti that > will force others to use the arago distribution, I wouldask that > we make sure the same applies for Angstrom as well, or any other > distribution for that matter. >=20 > So show me where it is being forced. Really. There are no > requires, only includes. So if you mean by 'forcing' that a few > warnings may scroll by than, yes, it's being 'forced'. If you > mean that the only way to use meta-ti is by using angstrom, than > no, it's not being 'forced'. So instead of spreading more FUD, > can you please use more precise language for the problem at hand? > As I said above, I agree that those images don't belong in meta- > ti. But funnily enough, that was not my decision. I was told to > keep them there. By TI. Who told you to keep these here? Now that we have a better understanding o= f the layers and their purpose I'll close the loop within TI to make sure w= e give a single answer. >=20 > > I'm confused where the objection is to moving these recipes > that rely on the Angstrom layer into the actual Angstrom layer? >=20 > For one, it was TI that objected to it. I don't care if some part > of TI is now changing course on that. I care if some other part > of TI is going to change course again in a few weeks. Just make a > clear decision and stick with it instead of not doing a thing and > rekindling the same old discussion every other month. > For two: They don't belong in the angstrom layer either, they are > way too machine/SoC specific for that. >=20 > > Let's discuss that topic and how we can structure this layer > to meet everyone's needs. That would likely be more productive > and save us all frustration. >=20 > Like I said, I have no problem at all removing all beagle, bone > and panda related things from meta-ti. In a previous incarnation > of this discussion I offered to do that and was told by TI to > keep everything in, both by SDO and AMBU people. So I'll offer it > again now. So if you don't like that proposal, make a counter > proposal. > Being an external contributor for the past 6 months has given me > a good sense of what works and what doesn't work and what the > level of (non)support the community can expect from TI. To be > clear: Denys is doing an awesome job managing meta-ti, someone > send him some cookies. Let's consider a meta-beagle layer. I'm thinking we should work to have me= ta-ti be a baseline of components we can agree on and move the rest to the = appropriate layer. >=20 > You work for TI, you get to dictate what happens in meta-ti, so > make a proposal. I'm only a small part of the community, I have > no illusions of being able to influence the direction of meta-ti. > I can however look at your proposal and give my opinion on it. > _______________________________________________ > meta-ti mailing list > meta-ti@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-ti From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-f176.google.com (mail-we0-f176.google.com [74.125.82.176]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1C067E01430 for ; Thu, 13 Sep 2012 16:16:44 -0700 (PDT) Received: by weyu3 with SMTP id u3so2481620wey.35 for ; Thu, 13 Sep 2012 16:16:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=DFz+mqaxUFZTMrmgiu3g432P63B3tSJBnhdFnl2QBOM=; b=l5R6JnA5STJP1cIsLK6SJNvyd2A0NgHIZggnSvvgnnhA0QxAQOQV14Tgi4KedGCp+b R2PDvfAqTGRtL5rf0iAKCifNF419nbhg5uy3bpEKve61NY0hecwlQxmbSG/mdStH+N2Q OFeoHb2Kn9b8lECBJjHAH4TR7K21bFklr/A/3k1jGoBksLsHjDYUXkSDE+XphRa99qOh WTvGQFia5fQ/rNhBLpc+t7egCdkBBOXxyzMZilN506VL0YicJa3/SLzQyOysiCR5AJHN 3IbSK/53i46uqV6D8bdl18zbKGsW3cxqXk0c0KDu7Fi7wMV6eQ/cz3t9Yt+GOAwC1Lpr qhKg== Received: by 10.216.133.148 with SMTP id q20mr312434wei.201.1347578203800; Thu, 13 Sep 2012 16:16:43 -0700 (PDT) Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by mx.google.com with ESMTPS id hv8sm10486wib.0.2012.09.13.16.16.42 (version=SSLv3 cipher=OTHER); Thu, 13 Sep 2012 16:16:42 -0700 (PDT) Received: by wgx1 with SMTP id 1so2105137wgx.11 for ; Thu, 13 Sep 2012 16:16:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.242.204 with SMTP id i54mr351751wer.94.1347578201752; Thu, 13 Sep 2012 16:16:41 -0700 (PDT) Received: by 10.223.144.133 with HTTP; Thu, 13 Sep 2012 16:16:41 -0700 (PDT) In-Reply-To: <7D46E86EC0A8354091174257B2FED101591C76F0@DLEE12.ent.ti.com> References: <8F29D6B095ED194EA1980491A5E029710C2B2B46@DFLE09.ent.ti.com> <20120901225617.GF22219@edge> <8F29D6B095ED194EA1980491A5E029710C2B34AD@DFLE09.ent.ti.com> <26A1186D-E714-4AD6-BB0E-1743FB6DFA2A@ti.com> <2A0DAC13-04B3-4E44-B278-B6A22233C86D@dominion.thruhere.net> <7D46E86EC0A8354091174257B2FED101591C76F0@DLEE12.ent.ti.com> Date: Thu, 13 Sep 2012 19:16:41 -0400 Message-ID: From: Jason Kridner To: "Maupin, Chase" X-Gm-Message-State: ALoCoQnsmJ1J0DoV/h/8VsjwOq0ZVt+8bFjKnTjPtH8K7dUgjkSyHi4eBFqxcuerumHLJCo5VoI+ Cc: "meta-ti@yoctoproject.org" Subject: Re: Fix image recipes in meta-ti X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 23:16:45 -0000 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 4, 2012 at 9:53 AM, Maupin, Chase wrote: >> -----Original Message----- >> From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti- >> bounces@yoctoproject.org] On Behalf Of Koen Kooi >> Sent: Sunday, September 02, 2012 4:11 PM >> To: meta-ti@yoctoproject.org >> Subject: Re: [meta-ti] Fix image recipes in meta-ti >> >> >> Op 2 sep. 2012, om 21:47 heeft "Maupin, Chase" >> het volgende geschreven: >> >> > I agree with Denys and Franklin here. Meta-ti should be a >> straight BSP layer so we should remove distro dependencies. This >> is the same as moving netbase changes to meta-arago. >> >> I'm not sure if what you mean by this example. The current >> netbase patch is the second try to get it into meta-ti, will >> there be a 3rd try? > > This will be moved to meta-arago based on your feedback. I think there were some questions about what you meant but it is understood now. > >> >> > There may be things in meta-ti that don't belong there and >> they should be moved to the appropriate location >> >> And I completely agree. >> >> > I understand that you have been using meta-ti and leading the >> way here, but that does not mean that we can't work together in >> this layer going forward. You may have noticed that most of the >> TI SDK stuff has been going into meta-arago since that is where >> it belongs. We are trying hard not to put things in meta-ti that >> will force others to use the arago distribution, I wouldask that >> we make sure the same applies for Angstrom as well, or any other >> distribution for that matter. >> >> So show me where it is being forced. Really. There are no >> requires, only includes. So if you mean by 'forcing' that a few >> warnings may scroll by than, yes, it's being 'forced'. If you >> mean that the only way to use meta-ti is by using angstrom, than >> no, it's not being 'forced'. So instead of spreading more FUD, >> can you please use more precise language for the problem at hand? >> As I said above, I agree that those images don't belong in meta- >> ti. But funnily enough, that was not my decision. I was told to >> keep them there. By TI. > > Who told you to keep these here? Now that we have a better understanding of the layers and their purpose I'll close the loop within TI to make sure we give a single answer. > >> >> > I'm confused where the objection is to moving these recipes >> that rely on the Angstrom layer into the actual Angstrom layer? >> >> For one, it was TI that objected to it. I don't care if some part >> of TI is now changing course on that. I care if some other part >> of TI is going to change course again in a few weeks. Just make a >> clear decision and stick with it instead of not doing a thing and >> rekindling the same old discussion every other month. >> For two: They don't belong in the angstrom layer either, they are >> way too machine/SoC specific for that. >> >> > Let's discuss that topic and how we can structure this layer >> to meet everyone's needs. That would likely be more productive >> and save us all frustration. >> >> Like I said, I have no problem at all removing all beagle, bone >> and panda related things from meta-ti. In a previous incarnation >> of this discussion I offered to do that and was told by TI to >> keep everything in, both by SDO and AMBU people. So I'll offer it >> again now. So if you don't like that proposal, make a counter >> proposal. >> Being an external contributor for the past 6 months has given me >> a good sense of what works and what doesn't work and what the >> level of (non)support the community can expect from TI. To be >> clear: Denys is doing an awesome job managing meta-ti, someone >> send him some cookies. > > Let's consider a meta-beagle layer. I'm thinking we should work to have meta-ti be a baseline of components we can agree on and move the rest to the appropriate layer. Chase, patches for meta-ti? Koen, if I am the one who directed you to keep beagle stuff in meta-ti (and I probably was and wasn't very specific in my language), it was for the purpose of having the highest degree of collaboration. I believe where we are landing is that the kernel mainline is the primary point of collaboration and other attempts to collaborate on a distro will mostly happen outside of meta-ti, such as in u-boot, oe-core, meta-oe, etc. I know Chase would like to keep meta-ti as a collaborative layer and I'm not aware of any efforts to remove kernel recipes, etc. for any of the platforms, but I'd like to free up any hard-and-fast directive that BeagleBoard.org distros need to be made using BSPs from meta-ti. While I certainly prefer if the TI SDK distro and BeagleBoard.org distro used the same BSP to help customers migrate between them, collaboration seems to be going well at a kernel and bootloader level without having the same BSP thanks to a focus on upstream contributions. I believe enabling everyone to work fast and efficiently on their own distros, the mainline kernels and mainline bootloaders is more critical than having a common BSP layer at this point. Let the flames begin, because I've probably said the wrong thing yet again, but I'm hopeful something will happen, even though I don't have a patch of my own here. > >> >> You work for TI, you get to dictate what happens in meta-ti, so >> make a proposal. I'm only a small part of the community, I have >> no illusions of being able to influence the direction of meta-ti. >> I can however look at your proposal and give my opinion on it. Denys, Chase, patches and statements as to what is and isn't allowed in meta-ti? >> _______________________________________________ >> meta-ti mailing list >> meta-ti@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/meta-ti > _______________________________________________ > meta-ti mailing list > meta-ti@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-ti