From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [RFC] Working toward a GNOME layer
Date: Thu, 21 Apr 2011 10:57:43 -0700 [thread overview]
Message-ID: <4DB07017.80503@linux.intel.com> (raw)
In-Reply-To: <6252772B-4D5D-4E5D-BCD5-1A53C1D25AFA@dominion.thruhere.net>
On 04/21/2011 10:29 AM, Koen Kooi wrote:
>
> Op 21 apr 2011, om 18:40 heeft Joshua Lock het volgende geschreven:
>
>> 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.
>>
>> I feel that Gtk+ is used by enough non-gnome software that it belongs in
>> core but others may disagree?
>>
I agree with Joshua here, I think that we need to keep some amount of
core gnome libraries in oe-core.
>> Between meta/recipes-gnome and meta-demoapps we have a reasonable start
>> to a meta-gnome/
>
> Where did meta-demoapps go? It's not in OE-core anymore by the looks of it.
>
Still there for me.
>> I'd be happy to help with this layer.
>
> Awesome, do you have any objection to put meta-gnome into the meta-openembedded repo for the time being? Once we get better tooling we can move it elsewhere, of course.
>
Why not on git.yoctoproject.org? We already have the start of various
meta-* layers there?
Sau!
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-04-21 18:00 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 [this message]
2011-04-21 19:23 ` Richard Purdie
2011-04-22 16:25 ` Joshua Lock
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=4DB07017.80503@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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