public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: akuster <akuster@mvista.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	 Armin Kuster <akuster808@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/5] [RFC] Move packages from meta-oe to core for X11
Date: Mon, 22 Dec 2014 18:14:52 -0800	[thread overview]
Message-ID: <5498D01C.9060301@mvista.com> (raw)
In-Reply-To: <CAJTo0LaOaz=vsqPPCy-f47vuAHx-rfgd7zZpLXNd3Qyhi36rww@mail.gmail.com>



On 12/22/2014 06:48 AM, Burton, Ross wrote:
> On 22 December 2014 at 04:54, Armin Kuster <akuster808@gmail.com
> <mailto:akuster808@gmail.com>> wrote:
>
>     This fixes 'core-image-x11' image dependancy on meta-oe packages
>     since xinit requires xterm, xclock and twm to 'startx'.
>
>
> Why can't we just make core-image-x11 start Matchbox instead?  Adding
> twm and xclock to oe-core seems crazy.

Crazy?? consider the source ; )   Let me look into matchbox, I am not 
familary with it.  I might be able to disable calling xterm, xclock and 
twm via configure.

   --with-twm=TWM          Path to twm
   --with-xclock=XCLOCK    Path to xclock
   --with-xterm=XTERM      Path to xterm

I wasn't a total waste. the recipes need some tlc.

Thanks for the response.

- Armin

>
> Ross
>
>


  reply	other threads:[~2014-12-23  2:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22  4:54 [PATCH 0/5] [RFC] Move packages from meta-oe to core for X11 Armin Kuster
2014-12-22  4:54 ` [[PATCH 1/5] xclock: move from meta-oe to core Armin Kuster
2014-12-22  4:54 ` [[PATCH 2/5] twm: " Armin Kuster
2014-12-22  4:54 ` [[PATCH 3/5] libxaw: " Armin Kuster
2014-12-22  4:55 ` [[PATCH 4/5] xterm: " Armin Kuster
2014-12-22  4:55 ` [[PATCH 5/5] xinit: fix depends issue Armin Kuster
2014-12-22 14:48 ` [PATCH 0/5] [RFC] Move packages from meta-oe to core for X11 Burton, Ross
2014-12-23  2:14   ` akuster [this message]
2014-12-23 15:59   ` akuster808
2014-12-31 13:35     ` Burton, Ross

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=5498D01C.9060301@mvista.com \
    --to=akuster@mvista.com \
    --cc=akuster808@gmail.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