Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: oe-core cleanup...
Date: Thu, 03 Mar 2011 13:09:17 +0000	[thread overview]
Message-ID: <1299157757.2550.5.camel@scimitar> (raw)
In-Reply-To: <41F9E0FC-E0A1-4C7F-8999-3E1B53FDDEE1@dominion.thruhere.net>

On Thu, 2011-03-03 at 13:46 +0100, Koen Kooi wrote:
> Op 2 mrt 2011, om 18:30 heeft Mark Hatle het volgende geschreven:
> 
> > I finally got a chance to look at the oe-core and where it currently is..  Some
> > suggestions below:
> > 
> > LICENSE file, this may need to be cleaned up to only cover the components
> > actually in the oe-core.
> > 
> > README likely needs some revision
> > 
> > README.hardware needs a lot of revision.  Anything outside of support for QEMU
> > should be removed.
> 
> Agreed on the above
> 
> > The meta-demoapps
> 
> That has a lot of GNOME bits I need, so I would suggest meta-oe, a seperate gnome layer or the easiest way, keep it as a seperate layer, but outside of yocto. I think a GNOME (2) layer would make a lot of sense, but I don't know how many people will be looking after it.
> With my beagleboard.org hat on, a full GNOME desktop is one of our deliverables to go on the SD card included with the board at the factory, so sorting out the duplication between the layers for GNOME components would be nice.

I'd be inclined to suggest the separate GNOME layer, though see below
for some further thoughts.

> 
> > and meta-rt components, will those be staying or going?
> 
> I don't have a real opinion on that.
> 
> > The meta/recipes.txt needs to be verified as still what we want -- I assume it
> > is at this point..
> 
> It looks OK to me
> 
> > meta/recipes-...  sato, qt, gnome, I thought were going elsewhere?
> 
> See above for GNOME layer, QT is likely a similar case. Layers would also benefit from having their own git repository, but I can see the combinatorial explosion that could bring.

I agree with this in principle, but before we dive into this we need to
decide where we draw the line. GNOME and Qt are not comparable. GNOME
and KDE are, Gtk+ and Qt are.

Where should Gtk+ and Qt live? E.g: if Gtk+ lives in meta-gnome does
that mean someone creating a meta-xfce needs to either a) provide their
own (copy of the) Gtk+ recipe OR b) depend on the meta-gnome's presence.

I'll accept "We'll cross that bridge when we come to it" as an answer
but I at least feel it's worth pointing this out.

Cheers,
Joshua
-- 
Joshua Lock
        Intel Open Source Technology Centre




  reply	other threads:[~2011-03-03 13:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 17:30 oe-core cleanup Mark Hatle
2011-03-02 18:00 ` Richard Purdie
2011-03-02 18:27   ` Koen Kooi
2011-03-02 18:33     ` Mark Hatle
2011-03-02 19:18     ` Richard Purdie
2011-03-03  0:58       ` Tom Rini
2011-03-03  8:02         ` Koen Kooi
2011-03-03 12:10           ` Richard Purdie
2011-03-03 14:43             ` Mark Hatle
2011-03-03 14:49               ` Tom Rini
2011-03-03 12:46 ` Koen Kooi
2011-03-03 13:09   ` Joshua Lock [this message]
2011-03-03 13:57     ` Koen Kooi
2011-03-03 14:05       ` Joshua Lock
2011-03-03 14:14         ` Chris Larson
2011-03-03 14:21           ` Chris Larson
2011-03-03 14:31             ` Joshua Lock
2011-03-03 14:29           ` Joshua Lock
2011-03-03 14:15       ` Chris Larson

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=1299157757.2550.5.camel@scimitar \
    --to=josh@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