Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: proposal to move cogl, clutter and related recipes from oe-core to dedicated meta-clutter layer
Date: Wed, 15 May 2013 18:22:42 +0100	[thread overview]
Message-ID: <5328014.mpvvKFpo4D@helios> (raw)
In-Reply-To: <5193B925.6010607@r-finger.com>

On Wednesday 15 May 2013 17:34:45 Tomas Frydrych wrote:
> On 15/05/13 15:09, Paul Eggleton wrote:
> > Can you not just get the appropriate changes into the BSP layers
> > so that when you add the BSP on top of OE-Core it does just work "out of
> > the box"?
> 
> What you are really saying is that the onus of maintaining working
> clutter packages should be on the BSP maintainers. I have already
> explained previously in this thread why I don't think this is going to
> work out in practice, so I am not going to repeat myself again.

No, I'm not. I'm saying configuration specific to a machine, if there is any, 
needs to be in the BSP layer for that machine. Whether the maintainer of that 
BSP or some external contributor provides and maintains that is a separate 
question.

If there are clutter tests we can run on the Yocto Project reference hardware 
platforms (which I understand from Bruce may be refreshed for 1.5) and they 
could be run in an automated manner, we can run these on the autobuilder and 
this will help prove the functionality of clutter itself. Once the tests are 
set up it should be easy for others to run these regularly on their own 
autobuilders with other BSPs.

> > If clutter is taken out of OE-Core this becomes even harder because then
> > BSPs can no longer bbappend clutter or cogl (if that is indeed what is
> > required in order to enable machine-specific functionality) without
> > fiddling around with BBMASK or keeping the appends in yet another
> > separate layer so they don't impact other BSP users who aren't building
> > Clutter.
> 
> The BSPs would not need to do anything regarding clutter, no bbappends,
> meta-clutter would be self-contained in this regard.

First you say there are hardware specific bits, then you say there aren't any 
changes required. I'm not following at all.

> I don't think there is any point in bothering the list with this
> discussion any further, we have gone around the circle more than once.

Sorry, but I don't think the important questions have been answered yet.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  parent reply	other threads:[~2013-05-15 17:41 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 15:11 proposal to move cogl, clutter and related recipes from oe-core to dedicated meta-clutter layer Tomas Frydrych
2013-05-08 15:23 ` Phil Blundell
2013-05-08 16:34   ` Tomas Frydrych
2013-05-08 15:23 ` Richard Purdie
2013-05-08 16:20   ` Tomas Frydrych
2013-05-10  9:05     ` Richard Purdie
2013-05-10 10:56       ` Tomas Frydrych
2013-05-10 11:32         ` Richard Purdie
2013-05-10 16:39           ` Tomas Frydrych
2013-05-10 17:19             ` Richard Purdie
2013-05-10 20:22               ` Otavio Salvador
2013-05-10 20:37                 ` Mark Hatle
2013-05-10 21:15                   ` Otavio Salvador
2013-05-13  9:30                   ` Tomas Frydrych
2013-05-13 15:41                     ` Phil Blundell
2013-05-13 15:44                       ` Burton, Ross
2013-05-14  9:14                       ` Tomas Frydrych
2013-05-14 16:55                         ` Paul Eggleton
2013-05-15  9:19                           ` Tomas Frydrych
2013-05-15  9:49                             ` Paul Eggleton
2013-05-15 11:35                               ` Tomas Frydrych
2013-05-15 11:53                                 ` Otavio Salvador
2013-05-15 13:20                                   ` Andreas Oberritter
2013-05-15 14:09                                 ` Paul Eggleton
2013-05-15 16:34                                   ` Tomas Frydrych
2013-05-15 16:54                                     ` Otavio Salvador
2013-05-15 17:22                                     ` Paul Eggleton [this message]
2013-05-15 17:30                                     ` Richard Purdie
2013-05-15 17:36                                       ` Otavio Salvador
2013-05-15 18:24                                         ` Paul Eggleton
2013-05-15 19:28                                           ` Otavio Salvador
2013-05-15 20:49                                             ` Phil Blundell
2013-05-16  9:01                                               ` Tomas Frydrych
2013-05-16 10:35                                                 ` Phil Blundell
2013-05-16 11:21                                                   ` Tomas Frydrych
2013-05-16 14:35                                                     ` Phil Blundell
2013-05-17 12:30                                                   ` Paul Eggleton
2013-05-16  9:22                                           ` Tomas Frydrych
2013-05-15 19:43                                       ` Richard Purdie
2013-05-16  9:21                                         ` Tomas Frydrych
2013-05-10 21:07                 ` Martin Jansa
2013-05-10 22:18                 ` Richard Purdie
2013-05-11 20:39                   ` Otavio Salvador
2013-05-11 21:49                     ` Richard Purdie
2013-05-14 16:23                       ` Philip Balister
2013-05-13  9:31                   ` Tomas Frydrych

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=5328014.mpvvKFpo4D@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox