All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: meta-ti?????
Date: Fri, 23 Dec 2011 10:01:09 -0500	[thread overview]
Message-ID: <4EF497B5.4020807@balister.org> (raw)
In-Reply-To: <7982955.p8V9rpaWRE@helios>

On 12/23/2011 08:43 AM, Paul Eggleton wrote:
> On Friday 23 December 2011 14:23:53 Koen Kooi wrote:
>>> Being a Yocto newbie, it's hard enough to understand all the branches on
>>> the yocto site. Relating the meta-angstrom is confusing.
>>
>> No, yocto (or is it poky? noone knows) 
> 
> Officially, Poky is the build system, Yocto is the umbrella project which also 
> includes a number of other sub-projects (swabber, pseudo, etc.). There are 
> some that use Yocto to refer to the build system; I'm not sure that does a 
> great deal of harm nor is it really relevant to this discussion.
> 
>> has confusing messaging, It's best to
>> find the official BSP for the board you use and follow the instructions in
>> there and ignore anything else.
> 
> Personally I think this is a bit disappointing. The Yocto Project and the move 
> to OE-Core is supposed to provide us a way to mix and match hardware support 
> with available software packages. The apparent tying of meta-texasinstruments 
> to meta-angstrom goes against that philosophy, IMHO. I haven't yet heard a 
> compelling technical argument for why that should be necessary.

BSP's shoudl contain image recipes that create useful images for the
hardware. Images often tend to contain distro specific bits and pieces.
This leads to this sort of (problematic) dependencies between layers.

This is good area for further study since the problem will likely
increase without careful thought. I'd also suggest not depending on the
BSP guys to do this, since I suspect their corporate overlords care more
about the output and customer satisfaction then internal "details".

Philip


  reply	other threads:[~2011-12-23 15:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22 15:06 meta-ti????? Jim Abernathy
2011-12-22 15:08 ` meta-ti????? Chris Larson
2011-12-23  8:28 ` meta-ti????? Koen Kooi
2011-12-23  8:37   ` meta-ti????? Paul Eggleton
2011-12-23  8:50     ` meta-ti????? Koen Kooi
2011-12-23 13:10       ` meta-ti????? James Abernathy
2011-12-23 13:23         ` meta-ti????? Koen Kooi
2011-12-23 13:43           ` meta-ti????? Paul Eggleton
2011-12-23 15:01             ` Philip Balister [this message]
2011-12-23 13:26         ` meta-ti????? Philip Balister
2011-12-23 17:10         ` meta-ti????? Bruce Ashfield
2011-12-23 17:38           ` meta-ti????? Philip Balister
2011-12-23 17:45             ` meta-ti????? Bruce Ashfield
2011-12-23 17:52               ` meta-ti????? Koen Kooi
2011-12-23 17:59                 ` meta-ti????? Bruce Ashfield
2012-01-04  5:15                   ` meta-ti????? Khem Raj
2012-01-04  5:17                     ` meta-ti????? Bruce Ashfield

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=4EF497B5.4020807@balister.org \
    --to=philip@balister.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=yocto@yoctoproject.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.