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.  There may be things in meta-ti that don't belong there 
and they should be moved to the appropriate location

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.

I'm confused where the objection is to moving these recipes that rely on the 
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

Sent from my iPad

On Sep 2, 2012, at 1:07 PM, "Cooper Jr., Franklin" <[email protected]> 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 unless 
> you depend on meta-angstrom which is wrong. As Denys' pointed out 
> (https://lists.yoctoproject.org/pipermail/meta-ti/2012-August/001452.html) 
> this is a "minor" issue but an issue that other people are experiencing.
> 
> 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 same 
> 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: [email protected] 
> [mailto:[email protected]] On Behalf Of Koen Kooi
> Sent: Sunday, September 02, 2012 11:17 AM
> To: Dmytriyenko, Denys
> Cc: [email protected]
> Subject: Re: [meta-ti] Fix image recipes in meta-ti
> 
> 
> Op 2 sep. 2012, om 00:56 heeft Denys Dmytriyenko <[email protected]> het volgende 
> geschreven:
> 
>> 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...
> 
> 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. 
> _______________________________________________
> meta-ti mailing list
> [email protected]
> https://lists.yoctoproject.org/listinfo/meta-ti
> _______________________________________________
> meta-ti mailing list
> [email protected]
> https://lists.yoctoproject.org/listinfo/meta-ti
_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

Reply via email to