From: "Belal, Awais" <Awais_Belal@mentor.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: GUI based images
Date: Mon, 8 May 2017 15:18:26 +0000 [thread overview]
Message-ID: <1494256705828.91940@mentor.com> (raw)
In-Reply-To: <935aef85-53ff-b5a6-5ce0-f95128778dd2@linux.intel.com>
> Generally, we have resources for maintaining only one GUI desktop in
> oe-core layer, and right now that is Sato. If you're okay with XFCE,
> that is provided via meta-xfce layer
I should probably quote every email on this thread and say THANKS! for the information and explanation.
BR,
Awais
________________________________________
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Sent: Monday, May 8, 2017 4:47 PM
To: Burton, Ross; Belal, Awais
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] GUI based images
On 05/08/2017 02:43 PM, Burton, Ross wrote:
> Obviously if you're happy to say "I target desktop users" then there's
> meta-gnome, meta-xfce, and so on.
I would not recommend meta-gnome, as it's not well maintained, and
should be used only for adding specific gnome apps to an image. It
doesn't define any full 'gnome images' or 'gnome packagegroups' that
would provide an integrated desktop.
Alex
next prev parent reply other threads:[~2017-05-08 15:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 10:51 GUI based images Belal, Awais
2017-05-08 11:33 ` Jussi Kukkonen
2017-05-08 11:39 ` Alexander Kanavin
2017-05-08 22:15 ` Paul Eggleton
2017-05-09 8:05 ` Alexander Kanavin
2017-05-09 8:44 ` Alex J Lennon
2017-05-09 9:18 ` Ian Arkver
2017-05-09 9:30 ` Alexander Kanavin
2017-05-09 9:31 ` Burton, Ross
2017-05-09 9:19 ` Alexander Kanavin
2017-05-09 11:17 ` Mike Looijmans
2017-05-09 9:24 ` Burton, Ross
2017-05-09 20:19 ` Khem Raj
2017-05-09 20:39 ` Alexander Kanavin
2017-05-09 20:59 ` Khem Raj
2017-05-09 21:03 ` Paul Eggleton
2017-05-09 22:27 ` Philip Balister
2017-05-10 9:31 ` Alexander Kanavin
2017-05-10 10:55 ` Paul Eggleton
2017-05-10 11:09 ` Alexander Kanavin
2017-05-10 20:15 ` Paul Eggleton
2017-05-11 7:43 ` Alexander Kanavin
2017-07-17 12:32 ` Jussi Kukkonen
2017-05-11 7:53 ` Alexander Kanavin
2017-05-15 12:36 ` Jussi Kukkonen
2017-05-15 15:56 ` Khem Raj
2017-05-08 11:43 ` Burton, Ross
2017-05-08 11:47 ` Alexander Kanavin
2017-05-08 15:18 ` Belal, Awais [this message]
2017-05-08 22:50 ` Khem Raj
2017-05-09 8:10 ` Alexander Kanavin
2017-05-09 19:43 ` Max Krummenacher
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=1494256705828.91940@mentor.com \
--to=awais_belal@mentor.com \
--cc=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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