Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] Working toward a GNOME layer
Date: Fri, 22 Apr 2011 09:25:11 -0700	[thread overview]
Message-ID: <1303489512.2293.7.camel@scimitar> (raw)
In-Reply-To: <1303413834.5518.361.camel@rex>

On Thu, 2011-04-21 at 20:23 +0100, Richard Purdie wrote:
> On Thu, 2011-04-21 at 09:40 -0700, Joshua Lock wrote:
> > On Thu, 2011-04-21 at 16:05 +0100, Paul Eggleton wrote:
> > > On Thursday 21 April 2011 15:02:49 Koen Kooi wrote:
> > > > and possibly more. I would like to create a meta-gnome layer in the
> > > > meta-openembedded repository where new recipes get added and things from
> > > > meta-demoapps can get moved over into. Long term recipes-gnome in oe-core
> > > > should move there as well.
> > > > 
> > > > What are your thoughts on this?
> > 
> > +1
> > 
> > > 
> > > From my perspective this sounds like a great idea. The only question would be 
> > > how much of the "GNOME" libs would remain in oe-core as some of them are quite 
> > > widely used outside of GNOME proper; however that can easily be worked out as 
> > > these things mature.
> > 
> > +1
> > 
> > My personal opinion would be that we start with glib & gtk+ (plus their
> > dependencies, i.e. pango, atk, etc) in core and move the rest out to a
> > layer.
> 
> Do we move out sato as well?
> 
> > I feel that Gtk+ is used by enough non-gnome software that it belongs in
> > core but others may disagree?
> 
> I think it needs to be in the core as we need something there to test
> X/graphics and so forth. This implies we need sato and its dependencies
> there too though (which are thankfully minimal by design).

I don't disagree with the need for a GUI in the core, my only concern is
that we'll have old/deprecated libraries in oe-core unless we find some
time to update Sato a bit.

Note: this is still on my To Do but isn't as high a priority as I might
like.

Cheers,
Joshua
-- 
Joshua Lock
        Yocto Build System Monkey
        Intel Open Source Technology Centre




      reply	other threads:[~2011-04-22 16:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 14:02 [RFC] Working toward a GNOME layer Koen Kooi
2011-04-21 15:05 ` Paul Eggleton
2011-04-21 16:40   ` Joshua Lock
2011-04-21 17:29     ` Koen Kooi
2011-04-21 17:41       ` Joshua Lock
2011-04-21 18:01         ` Koen Kooi
2011-04-21 18:12         ` Koen Kooi
2011-04-22 16:23           ` Joshua Lock
2011-04-22 17:34             ` Koen Kooi
2011-04-26 20:26               ` Joshua Lock
2011-04-21 17:57       ` Saul Wold
2011-04-21 19:23     ` Richard Purdie
2011-04-22 16:25       ` Joshua Lock [this message]

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=1303489512.2293.7.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